MIME-Version: 1.0
In-Reply-To: <54949108.3030109@vmware.com>
References: <548AF1CB.80702@vmware.com>
 <689EB259-44C2-4820-B901-4F6B1C55A1E4@simply.name>
 <549083D6.1000301@vmware.com>
 <CAHGQGwGJzp-QS7BODiv1uc291gAKtjzzCPb_nzUTxYKJhLsUCA@mail.gmail.com>
 <54949108.3030109@vmware.com>
Date: Sun, 1 Mar 2015 09:36:23 +1100
Message-ID: 
 <CAEyp7J9Hy8Q__FbGeR5skjk7d0dvLC+KLXB3JUuWrXXdJ5O+Wg@mail.gmail.com>
Subject: Re: Streaming replication and WAL archive interactions
From: Venkata Balaji N <nag1010@gmail.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, Borodin Vladimir <root@simply.name>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary=001a1137adcc68850905102d9d08
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

--001a1137adcc68850905102d9d08
Content-Type: text/plain; charset=UTF-8

>
>
> 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

--001a1137adcc68850905102d9d08
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><br>
Here&#39;s a first cut at this. It includes the changes from your standby_w=
al_archiving_v1.<u></u>patch, so you get that behaviour if you set archive_=
mode=3D&#39;always&#39;, and the new behaviour I wanted with archive_mode=
=3D&#39;shared&#39;. I wrote it on top of the other patch I posted recently=
 to not archive bogus recycled WAL segments after promotion (<a href=3D"htt=
p://www.postgresql.org/message-id/549489FA.4010304@vmware.com" target=3D"_b=
lank">http://www.postgresql.org/<u></u>message-id/549489FA.4010304@<u></u>v=
mware.com</a>), but it seems to apply without it too.<br>
<br>
I suggest reading the documentation changes first, it hopefully explains pr=
etty well how to use this. The code should work too, and comments on that a=
re welcome too, but I haven&#39;t tested it much. I&#39;ll do more testing =
next week.</blockquote><div><br></div><div>Patch did get applied successful=
ly to the latest master. Can you please rebase.</div><div><br></div><div>Re=
gards,</div><div>Venkata Balaji N</div><div><br></div><div><br></div></div>=
</div></div>

--001a1137adcc68850905102d9d08--