Re: Timeline following for logical slots - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Timeline following for logical slots
Date
Msg-id CAMsr+YH00gT9L5v2ieDA5KE6DCxZM3xK90_5WoA36oXzE6L7Pw@mail.gmail.com
Whole thread Raw
In response to Re: Timeline following for logical slots  (Andres Freund <andres@anarazel.de>)
Responses Re: Timeline following for logical slots
List pgsql-hackers
On 22 March 2016 at 19:48, Andres Freund <andres@anarazel.de> wrote:
On 2016-03-15 21:04:12 +0800, Craig Ringer wrote:
> Thanks very much for the review.

Are you planning to update the patch?


Updated patch attached.

It removes the questionable cleanups, fixes the randAccess comment (IMO),  changes the "open a new xlog segment" wording and explains why we don't need GetFlushRecPtr/GetXLogReplayRecPtr on replay of a historical timeline. I removed the change that did less than a whole page at the XLogRead call and instead added a comment explaining it. Fixed the brainfrart with candidate_restart_lsn, removed the outdated startptr comment and update and the unnecessary XLogReaderInvalCache call after it.

Also renamed src/test/modules/decoding_failover to src/test/modules/test_slot_timelines . Best name I could come up with that wasn't 1000chars long.

Passes main 'check', contrib/test_decoding check, src/test/modules/test_slot_timelines check and src/test/recovery check.

Available attached or at https://github.com/2ndQuadrant/postgres/tree/dev/logical-decoding-timeline-following .

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Odd system-column handling in postgres_fdw join pushdown patch
Next
From: Tatsuo Ishii
Date:
Subject: Re: multivariate statistics v14