Re: async streaming and recovery_target_timeline=latest - Mailing list pgsql-general

From Ben Chobot
Subject Re: async streaming and recovery_target_timeline=latest
Date
Msg-id 55E7F831-4449-467B-A73D-B4E5DF3DEA1A@silentmedia.com
Whole thread Raw
In response to Re: async streaming and recovery_target_timeline=latest  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-general
On Jul 28, 2013, at 5:29 PM, Amit Langote wrote:

I think, the WAL recycling on standby names the recycled segments with
the latest timelineID (in this case it's 0x10) which creates WALs that
there shouldn't have been like 000000100000146A00000001 instead of
0000000F0000146A00000001. This patch recently applied to 9.1.9 (but
not in any stable release so far) solves this problem as far as I can
see. Try and see if you can patch it:

http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=424cc31a3785bd01108e6f4b20941c6442d3d2d0

Thanks for the link Amit. That makes for 2 patches we're eagerly awaiting in 9.1.10.

pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [HACKERS] maintenance_work_mem and CREATE INDEX time
Next
From: Andrew Tipton
Date:
Subject: Re: Event trigger information accessibility on plpgsql