On Tue, 14 Aug 2012 10:50:07 -0700
Josh Berkus wrote:
>
> > Yeah, I think there's more people that agree with this use-case
> > than you seem to think.. That said, I appreciate that it's not a
> > trivial thing to support cleanly.
>
> Not trivial, no, but not major either. Really what needs t
> Yeah, I think there's more people that agree with this use-case than you
> seem to think.. That said, I appreciate that it's not a trivial thing
> to support cleanly.
Not trivial, no, but not major either. Really what needs to happen is
for the timeline change record to get transmitted over t
* Daniel Farina (dan...@heroku.com) wrote:
> On Mon, Aug 13, 2012 at 5:32 PM, Josh Berkus wrote:
> > To date, I seem to be the only one convinced that this is an actual
> > deficiency ...
>
> It is an actual deficiency, and I am convinced.
Yeah, I think there's more people that agree with this u
On Mon, Aug 13, 2012 at 5:32 PM, Josh Berkus wrote:
> To date, I seem to be the only one convinced that this is an actual
> deficiency ...
It is an actual deficiency, and I am convinced.
--
fdr
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subs
On 14/08/12 12:32, Josh Berkus wrote:
Mark,
Looking at the docs (section 25.2.6 paragraph 6) leads one to believe
that downstream standbys can continue to receive and process wal merely
by reconnecting after the cascading standby is promoted - but this does
not seem to be the case (indeed the s
Mark,
> Looking at the docs (section 25.2.6 paragraph 6) leads one to believe
> that downstream standbys can continue to receive and process wal merely
> by reconnecting after the cascading standby is promoted - but this does
> not seem to be the case (indeed the same paragraph notes that timeline
Looking at the docs (section 25.2.6 paragraph 6) leads one to believe
that downstream standbys can continue to receive and process wal merely
by reconnecting after the cascading standby is promoted - but this does
not seem to be the case (indeed the same paragraph notes that timelines
now no lo
