Re: Streaming replication and WAL archive interactions - Mailing list pgsql-hackers

From Venkata Balaji N
Subject Re: Streaming replication and WAL archive interactions
Date
Msg-id CAEyp7J9Hy8Q__FbGeR5skjk7d0dvLC+KLXB3JUuWrXXdJ5O+Wg@mail.gmail.com
Whole thread Raw
In response to Re: Streaming replication and WAL archive interactions  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Streaming replication and WAL archive interactions
List pgsql-hackers

Here's a first cut at this. It includes the changes from your standby_wal_archiving_v1.patch, so you get that behaviour if you set archive_mode='always', and the new behaviour I wanted with archive_mode='shared'. I wrote it on top of the other patch I posted recently to not archive bogus recycled WAL segments after promotion (http://www.postgresql.org/message-id/549489FA.4010304@vmware.com), but it seems to apply without it too.

I suggest reading the documentation changes first, it hopefully explains pretty well how to use this. The code should work too, and comments on that are welcome too, but I haven't tested it much. I'll do more testing next week.

Patch did get applied successfully to the latest master. Can you please rebase.

Regards,
Venkata Balaji N


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: CATUPDATE confusion?
Next
From: Stephen Frost
Date:
Subject: Re: CATUPDATE confusion?