Skip site navigation (1) Skip section navigation (2)

Re: pg_dump additional options for performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_dump additional options for performance
Date: 2008-07-26 16:24:07
Message-ID: 23580.1217089447@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Stephen Frost <sfrost(at)snowman(dot)net> writes:
>>> Another issue is that the rules for deciding which objects are "before
>>> data" and which are "after data" are wrong.  In particular ACLs are after
>>> data not before data, which is relatively easy to fix.  
>> 
>> OK

> This was partially why I was complaining about having documentation, and
> a policy for that matter, which goes into more detail about why X is before
> or after the data.  I agree that they're after today, but I don't see
> any particular reason why they should be one or the other.

If a table's ACL revokes owner insert privilege, and was placed before
the data load steps, those steps would fail.  We are relying on the
default table privileges until we are done doing everything we need to
do to the tables (and perhaps other objects, I'm not sure if there are
any other comparable problems).

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Stephen FrostDate: 2008-07-26 16:43:55
Subject: Re: pg_dump additional options for performance
Previous:From: Tom LaneDate: 2008-07-26 16:20:04
Subject: Re: pg_dump additional options for performance

pgsql-patches by date

Next:From: Stephen FrostDate: 2008-07-26 16:43:55
Subject: Re: pg_dump additional options for performance
Previous:From: Tom LaneDate: 2008-07-26 16:20:04
Subject: Re: pg_dump additional options for performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group