| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Ensure all implicit constraints are named |
| Date: | 2003-06-05 09:24:46 |
| Message-ID: | 1054805085.26169.15.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Thu, 2003-06-05 at 01:53, Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > [above]
>
> Er, weren't you just arguing for the opposite?
Yes, I was. Until I realized that some things in pg_dump depend on the
specific name of the constraint in cases where they are auto-generated.
To fix the problem, they need to be common.
Someday I'll probably propose that cluster should work on a list of
columns, and build the index by itself if one is not already available.
Once thats done, we can probably revisit pg_dump and make these items
unnamed in the dump file.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2003-06-05 09:33:57 | Re: pgstattuple for schemas |
| Previous Message | Tom Lane | 2003-06-05 05:55:17 | Re: pgstattuple for schemas |