From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Tom Lane" <tgl(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql/ oc/src/sgml/catalogs.sgml oc/src/sgml/r ... |
Date: | 2002-07-13 05:35:31 |
Message-ID: | 018f01c22a2f$1b389e00$0200a8c0@SOL |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Is it at all a problem that several columns in pg_conversion have the same
name as columns in pg_constraint?
Should the ones in pg_conversion become: convname instead of conname, etc.
simply for clarity?
Chris
----- Original Message -----
> Log message:
> Second phase of committing Rod Taylor's pg_depend/pg_constraint patch.
> pg_relcheck is gone; CHECK, UNIQUE, PRIMARY KEY, and FOREIGN KEY
> constraints all have real live entries in pg_constraint. pg_depend
> exists, and RESTRICT/CASCADE options work on most kinds of DROP;
> however, pg_depend is not yet very well populated with dependencies.
> (Most of the ones that are present at this point just replace formerly
> hardwired associations, such as the implicit drop of a relation's pg_type
> entry when the relation is dropped.) Need to add more logic to create
> dependency entries, improve pg_dump to dump constraints in place of
> indexes and triggers, and add some regression tests.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-13 17:07:52 | Re: [COMMITTERS] pgsql/ oc/src/sgml/catalogs.sgml oc/src/sgml/r ... |
Previous Message | Bruce Momjian - CVS | 2002-07-13 02:42:16 | pgsql/doc TODO |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2002-07-13 06:25:21 | Re: pgbench questions |
Previous Message | Rod Taylor | 2002-07-13 05:33:07 | Re: Unique and Primary Key Constraints |