Hi,
TimescaleDB as a Postgresql extension has been used in my firm for two
years now, I've recently managed to upgrade it from pg10 to pg12 and from
discrete VM's to Kubernetes as well.
Frankly speaking, being new to TimescaleDB at that time, I've found it easy
to manage, easy to scale (it's 100% c
Hi,
I'm using Wal-G like this, in pg12:
archive_mode = always
> archive_command = 'wal-g wal-push %p'
> archive_timeout = 60
> restore_command = 'wal-g wal-fetch %f %p'
The only change for pg10 is last line (restore_command) has to go into a
separate file, recovery.conf.
Please note, however, I
Hi,
Postgresql 11 already changed the position of replication parameters, now
all hosted in the main postgresql.conf file.
So on the standby node, instead of a recovery.conf file, just an empty
STANDBY.SIGNAL file is needed in the $PGDATA directory to start Postgresql
as a standby replica on that n
