help with startup slave after pg_rewind

2018-09-19 Thread Dylan Luong
Hi After promoting slave to master, I completed a pg_rewind of the slave (old master) to the new master. But when I try to start the slave I am getting the following error. 2018-09-20 07:53:51 ACST [20265]: [2-1] db=[unknown],user=replicant app=[unknown],host=10.69.20.22(51271) FATAL: the dat

Point-in-time recovery after failover

2018-03-13 Thread Dylan Luong
Hi We are on Postgres 9.6 and we have primary/standby wal replication setup for HA. For PITR, we have scheduled nightly base backup and hourly archive backups on the primary server. https://www.postgresql.org/docs/9.6/static/continuous-archiving.html I am trying to perform a point-in-time recov

RE: Resync second slave to new master

2018-03-08 Thread Dylan Luong
Thanks! That fixed the issue. -Original Message- From: Michael Paquier [mailto:mich...@paquier.xyz] Sent: Thursday, 8 March 2018 6:41 PM To: Yavuz Selim Sertoğlu Cc: Dylan Luong ; pgsql-generallists.postgresql.org Subject: Re: Resync second slave to new master On Thu, Mar 08, 2018 at

RE: Resync second slave to new master

2018-03-07 Thread Dylan Luong
-rw---. 1 postgres postgres 16777216 Mar 8 17:14 000601BB00B5 -rw---. 1 postgres postgres 218 Mar 8 16:48 0006.history Any ideas? Dylan -Original Message- From: Michael Paquier [mailto:mich...@paquier.xyz] Sent: Tuesday, 6 March 2018 5:55 PM To: Dylan Luon

RE: Resync second slave to new master

2018-03-05 Thread Dylan Luong
original configuration. -Original Message- From: Michael Paquier [mailto:mich...@paquier.xyz] Sent: Tuesday, 6 March 2018 3:54 PM To: Dylan Luong Cc: pgsql-generallists.postgresql.org Subject: Re: Resync second slave to new master On Tue, Mar 06, 2018 at 04:45:10AM +, Dylan Luong

Resync second slave to new master

2018-03-05 Thread Dylan Luong
Hi We are currently on PostgreSQL 9.6 and our HA is configured as master/slave with wal streaming replication. We would like to setup a second slave which replicates from the same master. Eg: Current setup: Slave <-- Master Slave is setup for automatic failover and we use pg_rewind after failo

RE: Performance issues during backup

2018-02-22 Thread Dylan Luong
Benavides [mailto:rene.romer...@gmail.com] Sent: Wednesday, 21 February 2018 1:37 AM To: Laurenz Albe Cc: Dylan Luong ; pgsql-general@lists.postgresql.org Subject: Re: Performance issues during backup What about sending the backup to a different server? through ssh / rsync or something, that

Performance issues during backup

2018-02-19 Thread Dylan Luong
Hi We perform nighty base backup of our production PostgreSQL instance. We have a script that basically puts the instance into back mode and then backs up (tar) the /Data directory and then takes it out of backup mode. Ie, psql -c "SELECT pg_start_backup('${DATE}');" tar -cvf - ${DATA_DIR} --exc

RE: Missing WAL file after running pg_rewind

2018-01-14 Thread Dylan Luong
not from C0? Dylan -Original Message- From: Michael Paquier [mailto:michael.paqu...@gmail.com] Sent: Saturday, 13 January 2018 9:04 PM To: Dylan Luong Cc: pgsql-general@lists.postgresql.org Subject: Re: Missing WAL file after running pg_rewind On Fri, Jan 12, 2018 at 09:44:25PM +

RE: Missing WAL file after running pg_rewind

2018-01-12 Thread Dylan Luong
] Sent: Friday, 12 January 2018 12:08 PM To: Dylan Luong Cc: pgsql-general@lists.postgresql.org Subject: Re: Missing WAL file after running pg_rewind On Thu, Jan 11, 2018 at 04:58:02PM +, Dylan Luong wrote: > The steps I took were: > > 1. Stop all watchdogs > > 2.

Missing WAL file after running pg_rewind

2018-01-11 Thread Dylan Luong
Hi We had a failover situation where our monitoring watchdog processes promoted the slave to become the new master. I restarted the old master database to ensure a clean stop/start and performed pg_rewind on the old master to resync with the new master. However, after successful rewind, there w

RE: clean out ./data/base/pgsql_tmp

2017-12-06 Thread Dylan Luong
: Dylan Luong Cc: pgsql-general@lists.postgresql.org Subject: Re: clean out ./data/base/pgsql_tmp On Thu, Dec 7, 2017 at 5:18 PM, Dylan Luong wrote: > We have an issue where one of the developers ran a large query that > hung was filling up the DATA drive very rapidly. From 50% usage

clean out ./data/base/pgsql_tmp

2017-12-06 Thread Dylan Luong
Hi We have an issue where one of the developers ran a large query that hung was filling up the DATA drive very rapidly. From 50% usage to 95% in less than 2hrs. It created a very large pgsql_tmp size (300GB). To stop the drive filling up we had to kill the process manually using kill -9. How do