From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: LSN as a recovery target |
Date: | 2016-05-24 04:29:22 |
Message-ID: | CAB7nPqQRXsC8=ozh6GpjLnpZ=MeooUZOaAbzx28n2bjSMv2B4g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 23, 2016 at 6:25 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 24 May 2016 at 09:12, Michael Paquier <michael(dot)paquier(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2016-05-24 06:03:07 | Is the unfair lwlock behavior intended? |
Previous Message | Tom Lane | 2016-05-24 04:28:40 | Re: PATCH: Batch/pipelining support for libpq |