From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [8.0.3] Not dumping all sequences ... |
Date: | 2005-08-03 02:45:22 |
Message-ID: | 42F02FC2.2000301@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I should point out that the bug I reported about dependencies and
changing the type of a serial column still exists.
Once you change a serial column to something else, you cannot ever
change the default IIRC...
Chris
Tom Lane wrote:
> "Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
>
>>On Tue, 2 Aug 2005, Tom Lane wrote:
>>
>>>Well, that second line is *definitely* a SERIAL column linkage.
>>>
>>>Is it possible they did "create table xa_url(id bigserial, ...)" and
>>>then later changed the default expression for the column?
>
>
>>'k, am checking into this ... is it a simple matter of removing that
>>second record above from pg_depend to "fix" the pg_dump issue, or
>>something more involved then that?
>
>
> AFAIR, removing that pg_depend entry would be enough to decouple the
> sequence so it appears as an independent object in the pg_dump output.
> However, I'm still wondering exactly what is wrong, if anything ---
> does the pg_dump output not reload correctly? If so, what happens
> exactly when you try?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2005-08-03 08:31:46 | Re: Information Schema DBMS VERSION wrong |
Previous Message | Tom Lane | 2005-08-03 02:19:54 | Re: [8.0.3] Not dumping all sequences ... |