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

Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences:

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences:
Date: 2005-03-26 06:30:13
Message-ID: 42450175.4070606@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
> Fix two bugs in change_owner_recurse_to_sequences: it was grabbing an
> overly strong lock on pg_depend, and it wasn't closing the rel when done.
> The latter bug was masked by the ResourceOwner code, which is something
> that should be changed.

I assume that this behaviour makes change owner on a table change owner 
of serial sequences?

Should we perhaps also propagate grant insert on a table to grant 
select, update on dependent serial sequences?

Chris

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-03-26 06:35:20
Subject: Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was
Previous:From: Marc G. FournierDate: 2005-03-26 04:10:58
Subject: 8.0.2beta1 ... look her over ...

pgsql-committers by date

Next:From: Tom LaneDate: 2005-03-26 06:35:20
Subject: Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was
Previous:From: Tom LaneDate: 2005-03-26 06:28:59
Subject: pgsql: Use a bitmapset instead of a list for duplicate-column checking

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