Postgres Pro
Downloads
Home   >   mailing lists

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

From Simon Riggs
Subject Re: pg_dump broken for non-super user
Date
Msg-id CANP8+j+CqU9vCqPV3m34oi8-C-0N4+PjfvkurAfpTo5sXZ4o8w@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump broken for non-super user  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump broken for non-super user
List pgsql-hackers
Tree view
On 4 May 2016 at 16:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
 
Why is it that we need to lock a table at all if we're just going to dump
its ACL? 

We don't, but surely that's the wrong question.

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?

For what reason are we changing existing behaviour? There is no bug here, as Stephen explained.

So this is a behaviour change after freeze with uncertain purpose.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [COMMITTERS] pgsql: Add TAP tests for pg_dump
Next
From: Masahiko Sawada
Date:
Subject: Re: Reviewing freeze map code