On 06/10/2019 04:37 PM, Kuntal Ghosh wrote:
When we define a restore command, we tell the server to copy a file a
WAL file from the archive. So, it should be
restore_command='cp tmp/archive_dir1/%f %p'
This is the reason you're getting this following error.
Ohh. Mea Culpa.
Thanks for
On Mon, Jun 10, 2019 at 07:56:12PM +0530, Kuntal Ghosh wrote:
> On Mon, Jun 10, 2019 at 7:19 PM Robert Haas wrote:
>> This whole thing looks like a nonissue to me. If you set it up wrong,
>> it won't work. So don't do that.
+1.
--
Michael
signature.asc
Description: PGP signature
On Mon, Jun 10, 2019 at 7:19 PM Robert Haas wrote:
>
> On Mon, Jun 10, 2019 at 7:08 AM Kuntal Ghosh
> wrote:
> > This can surely be fixed from the script. While configuring the old
> > master as a standby server, clear/modify the settings in
> > postgresql.auto.conf. But, it contradicts with
On Mon, Jun 10, 2019 at 7:08 AM Kuntal Ghosh wrote:
> This can surely be fixed from the script. While configuring the old
> master as a standby server, clear/modify the settings in
> postgresql.auto.conf. But, it contradicts with the comment in the file
> which forbids the user from editing the
Hello,
On Wed, Jun 5, 2019 at 11:55 AM tushar wrote:
I can see two different problems in this setup.
> > 2)Slave Setup -> ./pg_basebackup -PR -X stream -c fast -h 127.0.0.1
> > -U centos -p 5432 -D slave
> > restore_command='cp %p /tmp/archive_dir1/%f'
> > "
> > 7)Modify old
Hi,
Is anyone able to reproduce this one ?
Any pointer to solve this would be helpful.
regards,
On 05/27/2019 07:27 PM, tushar wrote:
Hi,
I am getting this below error - after performing pg_rewind when i try
to start new slave ( which earlier was my master) against PGv12 Beta1.
"
cp:
Hi,
I am getting this below error - after performing pg_rewind when i try to
start new slave ( which earlier was my master) against PGv12 Beta1.
"
cp: cannot stat ‘pg_wal/RECOVERYHISTORY’: No such file or directory
2019-05-27 18:55:47.387 IST [25500] LOG: entering standby mode
cp: cannot stat
