On Sun, Aug 08, 2004 at 12:50:43PM +0800, Christopher Kings-Lynne wrote:
> 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.
System catalogs screws are possible.
That someone is probably me, but I don't remember pg_dump
giving me any warning about this. Also I think I've run vacuum
on the db before dumping.
As before I'm not on the source computer so I can't send the
pg_dump -s, but if you want, I can send you the pg_restore -l.
--strk;
>
> 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
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
