From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jonathan Vanasco <postgres(at)2xlp(dot)com> |
Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: bug in schema export? |
Date: | 2007-04-17 18:51:46 |
Message-ID: | 4588.1176835906@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jonathan Vanasco <postgres(at)2xlp(dot)com> writes:
> i believe i found a bug
> psql> create table test_failure ( id integer primary key );
> psql> alter table test_failure alter id rename to id_new ; # not
> relevant, just illustrating the reason how i got to step 2
> psql> alter table test_failure_pkey rename to test_failure_id_new_pkey;
> $ pg_dump --schema-only -ttest_failure -Utest > test.sql
> the pkey in the schema is added as 'test_failure_pkey' , not
> 'test_failure_id_new_pkey';
You didn't rename the constraint. If we were going to do anything about
this, it'd be to forbid directly renaming indexes that're owned by
constraints. However, since we don't currently have a RENAME CONSTRAINT
command, the effect of that would be that you couldn't do it at all ...
In the meantime you can probably do an UPDATE on pg_constraint if you
really care.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sven Willenberger | 2007-04-17 20:32:25 | Re: postgresql 8.1.4 to 8.2.3 |
Previous Message | Jonathan Vanasco | 2007-04-17 18:33:17 | bug in schema export? |