Skip to content

Latest commit

 

History

History
106 lines (67 loc) · 4.06 KB

File metadata and controls

106 lines (67 loc) · 4.06 KB
title excerpt products keywords
Install TimescaleDB on Windows
Install self-hosted TimescaleDB on Windows
self_hosted
installation
self-hosted
Windows

import Windows from "versionContent/_partials/_psql-installation-windows.mdx"; import WhereTo from "versionContent/_partials/_where-to-next.mdx"; import TestingEnv from "versionContent/_partials/_selfhosted_production_alert.mdx" ; import SelfHostedWindowsBased from "versionContent/_partials/_install-self-hosted-windows-based.mdx"; import AddTimescaleDBToDB from "versionContent/_partials/_add-timescaledb-to-a-database.mdx"; import WindowsSupport from "versionContent/_partials/_timescaledb_supported_windows.mdx";

Install $TIMESCALE_DB on Windows

$TIMESCALE_DB is a $PG extension for time series and demanding workloads that ingest and query high volumes of data.

This section shows you how to:

< TestingEnv />

Prerequisites

To install $TIMESCALE_DB on your Windows device, you need:

Install and configure $TIMESCALE_DB on $PG

This section shows you how to install the latest version of $PG and $TIMESCALE_DB on a supported platform using the packages supplied by $COMPANY.

If you have previously installed $PG without a package manager, you may encounter errors following these install instructions. Best practice is to full remove any existing $PG installations before you begin.

To keep your current $PG installation, Install from source.

Add the $TIMESCALE_DB extension to your database

For improved performance, you enable $TIMESCALE_DB on each database on your self-hosted $PG instance. This section shows you how to enable $TIMESCALE_DB for a new database in $PG using psql from the command line.

And that is it! You have $TIMESCALE_DB running on a database on a self-hosted instance of $PG.

Supported platforms

The latest $TIMESCALE_DB releases for $PG are:

You can deploy $TIMESCALE_DB on the following systems:

For release information, see the GitHub releases page and the release notes.

Where to next