Re: Review: Patch to compute Max LSN of Data Pages

From: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
To: "'Andres Freund'" <andres(at)2ndquadrant(dot)com>
Cc: "'Hari Babu'" <haribabu(dot)kommi(at)huawei(dot)com>, "'Robert Haas'" <robertmhaas(at)gmail(dot)com>, "'Josh Berkus'" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Review: Patch to compute Max LSN of Data Pages
Date: 2013-07-08 13:54:26
Message-ID: 016c01ce7be2$a9465ff0$fbd31fd0$@kapila@huawei.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday, July 08, 2013 5:16 PM Andres Freund wrote:
> On 2013-07-08 17:10:43 +0530, Amit Kapila wrote:
> > On Monday, July 08, 2013 4:26 PM Andres Freund wrote:
> > > On 2013-07-08 16:17:54 +0530, Hari Babu wrote:
> > > > + This utility can also be used to decide whether backup is
> > > required or not when the data page
> > > > + in old-master precedes the last applied LSN in old-standby
> > > (i.e., new-master) at the
> > > > + moment of the failover.
> > > > + </para>
> > > > + </refsect1>
> > >
> > > I don't think this is safe in any interesting set of cases. Am I
> > > missing
> > > something?
> >
> > No, you are not missing anything. It can be only used to find max LSN
> in
> > database which can avoid further corruption
>
> Why is the patch submitted documenting it as a use-case then?

This is my mistake, I was not able to catch.
I am really sorry for it and in future will make sure such mistake doesn't
happen again

> I find it
> rather scary if the *patch authors* document a known unsafe use case as
> one of the known use-cases.

With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2013-07-08 14:05:31 Re: Improving avg performance for numeric
Previous Message Tom Lane 2013-07-08 13:08:57 Re: [9.3 bug fix] backends emit hundreds of messages when statistics file is inaccessible