| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was |
| Date: | 2005-03-25 18:04:48 |
| Message-ID: | 20050325180448.473A6538B9@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Log Message:
-----------
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.
Tags:
----
REL8_0_STABLE
Modified Files:
--------------
pgsql/src/backend/commands:
tablecmds.c (r1.142.4.2 -> r1.142.4.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablecmds.c.diff?r1=1.142.4.2&r2=1.142.4.3)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-03-25 18:17:14 | pgsql: Have libpgport link before libpq so that PG client applications |
| Previous Message | Tom Lane | 2005-03-25 18:04:34 | pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GUNDUZ | 2005-03-25 18:18:56 | Re: pg_dump issue : Cannot drop a non-existent(?) trigger |
| Previous Message | Tom Lane | 2005-03-25 15:35:54 | Re: pg_dump issue : Cannot drop a non-existent(?) trigger |