| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-26 06:35:20 | Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was |
| Previous Message | Tom Lane | 2005-03-26 06:28:59 | pgsql: Use a bitmapset instead of a list for duplicate-column checking |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-26 06:35:20 | Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was |
| Previous Message | Marc G. Fournier | 2005-03-26 04:10:58 | 8.0.2beta1 ... look her over ... |