You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the performance optimization technique for insertion according
to Timescaledb blog is to use separate disks for WAL & data.
According to blog [1],
```
Use separate disks for WAL and data
-----------------------------------
While this is a more advanced optimization that isn't always needed, if your disk becomes a bottleneck,
you can further increase throughput by using a separate disk (tablespace) for the database's write-ahead log (WAL) and data.
```
[1] https://www.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/
- **PGROOT**: a directory where we put the pgdata (by default /home/postgres/pgroot). One may adjust it to point to the mount point of the persistent volume, such as EBS.
18
18
- **WALE_TMPDIR**: directory to store WAL-E temporary files. PGROOT/../tmp by default, make sure it has a few GBs of free space.
19
19
- **PGDATA**: location of PostgreSQL data directory, by default PGROOT/pgdata.
20
+
- **WAL_DIRECTORY**: location where the write-ahead log should be stored. By default stored inside PGDATA. This option is useful if you plan to use separate disks for WAL and data.
20
21
- **PGUSER_STANDBY**: username for the replication user, 'standby' by default.
21
22
- **PGPASSWORD_STANDBY**: a password for the replication user, 'standby' by default.
22
23
- **STANDBY_HOST**: hostname or IP address of the primary to stream from.
0 commit comments