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

Re: Permissions problem with sequences

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Gary Doades <gpd(at)gpdnet(dot)co(dot)uk>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Permissions problem with sequences
Date: 2004-09-26 03:08:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thu, Sep 23, 2004 at 07:29:47PM -0400, Tom Lane wrote:
> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > There is, however, an ownership problem with restoring sequences
> > in 8.0.0beta.  In 7.4.5, for example, pg_dump issues a SET SESSION
> > AUTHORIZATION command and then creates a table, so implicitly-created
> > sequences are restored with the correct ownership.  In 8.0.0beta2,
> > however, pg_dump doesn't issue SET SESSION AUTHORIZATION but rather
> > creates a table and then issues ALTER TABLE ... OWNER TO.
> > Oer.  I'd better look at that :(
> I think Alvaro's patch to make ALTER TABLE OWNER recurse to serial
> sequences fixes all the issues that were raised in this thread ---
> does anyone see any remaining problems?

Looks good so far.  I originally noticed the sequence ownership
problem when restoring a backup made with pg_dump, and that appears
to work now.


Michael Fuhr

In response to

pgsql-bugs by date

Next:From: Aleksey FedorchenkoDate: 2004-09-26 17:52:21
Subject: Re: BUG #1266: Improper unique constraint / MVCCactivitieswithin single transaction
Previous:From: Tom LaneDate: 2004-09-26 00:36:05
Subject: Re: BUG #1269: Copy To Gives Relative path error when explicit path given.

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