Re: LSN as a recovery target - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: LSN as a recovery target
Date
Msg-id CAB7nPqQRXsC8=ozh6GpjLnpZ=MeooUZOaAbzx28n2bjSMv2B4g@mail.gmail.com
Whole thread Raw
In response to Re: LSN as a recovery target  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: LSN as a recovery target  (Christoph Berg <myon@debian.org>)
List pgsql-hackers
On Mon, May 23, 2016 at 6:25 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
> On 24 May 2016 at 09:12, Michael Paquier <michael.paquier@gmail.com> wrote:
>>
>> Hi all,
>>
>> Today somebody has pointed me out that it could be interesting to be
>> able to recovery up to a given LSN position. One argument behind that
>> was to allow a maximum of things to recover up to the point where a
>> relation block got corrupted by a specific record because of a broken
>> segment. So that would be simply having recovery_target_lsn in
>> recovery.conf similar to what we have now.
>> Thoughts?
>>
>
> Sounds useful, if somewhat niche. I've needed that in the past, and just
> zeroed the WAL segment after the end of the target record. Not super
> user-friendly.

Yeah, that's really something that covers only a narrow case, though
if we don't have it when we need it we're limited to some hacks.
Perhaps people who have the advanced level to use such a thing have
the level to use hacks anyway..
-- 
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PATCH: Batch/pipelining support for libpq
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: Is the unfair lwlock behavior intended?