Re: [GENERAL] CLOG read problem after pg_basebackup

2015-06-21 Thread Andres Freund
Hi, On 2015-01-23 15:31:15 +0100, Petr Novak wrote: > I'd like to ask for help clarifying an issue I'm having. > > I've recently prepared new servers in another datacenter for some of our > databases which I want to set up as a streaming replicas. There are several > instances(clusters) with size

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-24 Thread Adrian Klaver
On 01/23/2015 05:18 PM, David G Johnston wrote: Petr Novak wrote Three of them failed to start after pg_basebackup completed with: FATAL: could not access status of transaction 923709700 DETAIL: Could not read from file "pg_clog/0370" at offset 237568: Success. (the clog file differed in eac

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread David G Johnston
Petr Novak wrote > Three of them failed to start after pg_basebackup completed with: > > FATAL: could not access status of transaction 923709700 > DETAIL: Could not read from file "pg_clog/0370" at offset 237568: > Success. > > (the clog file differed in each case of course..) > > As for PG ve

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread Adrian Klaver
On 01/23/2015 08:55 AM, Petr Novak wrote: I've checked wal_keep_segments before i've started the backup and the xlog dir on the master contained logs from several hours ago. Which was sufficient. Also if this would be the case, then copying affected clog file from the master wouldn't solve the pr

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread Petr Novak
I've checked wal_keep_segments before i've started the backup and the xlog dir on the master contained logs from several hours ago. Which was sufficient. Also if this would be the case, then copying affected clog file from the master wouldn't solve the problem as the requires wals would be still mi

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread Adrian Klaver
On 01/23/2015 08:36 AM, Petr Novak wrote: Just the config files for the replica, all other dirs were removed. Alright, lets look at the other end. You are using -x which is: Using this option is equivalent of using -X with method fetch. and -X fetch is: f fetch The transaction log files ar

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread Petr Novak
Just the config files for the replica, all other dirs were removed. P On Jan 23, 2015 5:30 PM, "Adrian Klaver" wrote: > On 01/23/2015 08:21 AM, Petr Novak wrote: > >> Hi Adrian, >> >> sure the command is as follows: >> >> pg_basebackup -h -p -D /data2/pgsql/baseb -P -v -U >> replicator -x -c f

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread Adrian Klaver
On 01/23/2015 08:21 AM, Petr Novak wrote: Hi Adrian, sure the command is as follows: pg_basebackup -h -p -D /data2/pgsql/baseb -P -v -U replicator -x -c fast After that I moved the content of /data2/pgsql/baseb to actual datadir and tried to start up the cluster. Where there left over file

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread Petr Novak
Hi Adrian, sure the command is as follows: pg_basebackup -h -p -D /data2/pgsql/baseb -P -v -U replicator -x -c fast After that I moved the content of /data2/pgsql/baseb to actual datadir and tried to start up the cluster. On some servers it worked on the three didn't. The servers are of the sa

Re: [GENERAL] CLOG read problem after pg_basebackup

2015-01-23 Thread Adrian Klaver
On 01/23/2015 06:31 AM, Petr Novak wrote: Hi all, I'd like to ask for help clarifying an issue I'm having. I've recently prepared new servers in another datacenter for some of our databases which I want to set up as a streaming replicas. There are several instances(clusters) with size ranging f