Re: pg_dump broken for non-super user - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: pg_dump broken for non-super user
Date
Msg-id 20160507142121.GM10850@tamriel.snowman.net
Whole thread Raw
In response to Re: pg_dump broken for non-super user  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pg_dump broken for non-super user  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
* Simon Riggs (simon@2ndQuadrant.com) wrote:
> On 7 May 2016 at 16:14, Stephen Frost <sfrost@snowman.net> wrote:
> > > If we don't lock it then we will have a inconsistent dump that will fail
> > > later, if dumped while an object is being dropped.
> > > Do we want an inconsistent dump?
> >
> > The dump won't be inconsistent, as Tom pointed out.  The catalog tables
> > are read using a repeatable read transaction, which will be consistent.
>
> The scan is consistent, yes, but the results would not be.

I'm not following- the results are entirely dependent on the scan, so if
the scan is consistent, how could the results not be?

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pg_dump broken for non-super user
Next
From: Simon Riggs
Date:
Subject: Re: pg_dump broken for non-super user