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:50:43 |
Message-ID: | 4115B123.2010001@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Also, given this and your previous operator commutator problem, I
strongly suspect that someone has taken an axe to the system catalogs on
your installation and they are very screwy.
Chris
strk wrote:
> 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.
>
> 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 ?
>
> TIA
>
> --strk;
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-08 04:50:48 | Re: log file rotate |
Previous Message | Christopher Kings-Lynne | 2004-08-08 04:49:20 | Re: pg_dump and sequences (bug ?) |