| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LSN as a recovery target |
| Date: | 2016-05-24 01:25:31 |
| Message-ID: | CAMsr+YGsp=uJfyzD6VGk6wBpDhVUOrS1U6-gt8P4Qg+33njo-w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-05-24 01:27:44 | Re: Typo in 001_initdb.pl |
| Previous Message | Craig Ringer | 2016-05-24 01:20:43 | Re: PATCH: Batch/pipelining support for libpq |