| From: | Jeffrey Melloy <jmelloy(at)visualdistortion(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Renaming a schema |
| Date: | 2004-06-25 00:48:03 |
| Message-ID: | 50A428EB-C641-11D8-8DAF-000393C78AC0@visualdistortion.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jun 24, 2004, at 4:46 PM, Tom Lane wrote:
> Jeffrey Melloy <jmelloy(at)visualdistortion(dot)org> writes:
>> Recently, I decided to rename one of my schemas from "adium" to "im".
>> Then, all inserts started failing.
>> I recreated a couple functions, changed the search path, and all
>> inserts
>> are still failing due to referential integrity checks going against
>> "adium" still. Is there any way I can fix this, short of manually
>> dropping every constraint and recreating them?
>
> I couldn't replicate this ... AFAICS the RI triggers reference tables
> by
> OID, not name. What PG version are you using? Can you give a
> self-contained test case?
>
> regards, tom lane
>
I'm using PostgreSQL 7.4.2, and have a script that reproduces my
problem:
Upon further inspection, the problem isn't the RI triggers; it's the
default sequence not changing.
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2004-06-25 01:19:05 | Re: unicode and sorting(at least) |
| Previous Message | Tom Lane | 2004-06-24 21:46:49 | Re: Renaming a schema |