From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Fix for bug #2310-2 |
Date: | 2006-04-23 16:35:10 |
Message-ID: | 20060423163510.GA4621@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
In this email
http://archives.postgresql.org/pgsql-bugs/2006-03/msg00076.php
belonging to bug #2310, Tom says
> I wrote:
> > The relevant owner field for a composite type is pg_type.typowner.
> > We don't bother to maintain pg_class.relowner for the subsidiary
> > pg_class entry.
>
> Actually, now that I look at it, there is a non-cosmetic issue here:
> we seem to be creating a dependency link for the pg_class owner field.
> We have to either not do that, or be willing to fix it during ALTER TYPE
> OWNER.
This patch fixes this problem, by inhibiting the recording of the owner
in pg_shdepend for a RELKIND_COMPOSITE_TYPE relation (i.e. the first
solution proposed above). I intend to apply it to 8.1 and current
trunk, later today.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Attachment | Content-Type | Size |
---|---|---|
type-owner.patch | text/plain | 977 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-04-23 18:30:51 | Re: Additional current timestamp values |
Previous Message | Bruno Wolff III | 2006-04-23 15:08:01 | Re: [HACKERS] Automatically setting work_mem |