From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | strk <strk(at)keybit(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump and sequences (bug ?) |
Date: | 2004-08-08 04:49:20 |
Message-ID: | 4115B0D0.4070103@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Using pg_dump from postgresql 7.3.4 I've obtained
> a dump file containing a SEQUENCE SET with no
> corresponding SEQUENCE. I've seen that this is usually
> due to the presence of a table with a 'serial' field,
> but since in this case there is no such table I wonder
> if this is a bug in pg_dump.
Perhaps. Is there any way you can send me the compressed pg_dump -s
output of your database? Is it sensitive info? How certain are you
that there is no serial column in your database?
> The only reason I can imagine for this is pg_dump taking
> any sequence whose name ends in _seq as being associated
> to a table, no matter if that table exists and has a 'serial'
> field. Is this possible ? Shouldn't this kind of dependency
> be coded somehow ?
It is coded somehow and pg_dump in no way treats things that end in _seq
as being on tables.
My first suspicion is that you must be mistaken, but i would really like
to see the full pg_dump -s output of your database....
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-08-08 04:50:43 | Re: pg_dump and sequences (bug ?) |
Previous Message | Marc G. Fournier | 2004-08-08 03:49:32 | Re: beta time |