Re: pg_dumpall fails

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Willy Wonka <lunchtime(at)onethirty(dot)org>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dumpall fails
Date: 2002-09-28 03:38:00
Message-ID: 9642.1033184280@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Willy Wonka <lunchtime(at)onethirty(dot)org> writes:
> i don't know what my brother has been doing on the other end, but
> pg_dumpall now returns this:

> SELECT nextval ('"art_links_id_seq"');
> dumpSequence(submissions_submission_id_seq): different sequence name
> returned by SELECT: submissions_n_submission_id_seq

What he's been doing is renaming sequences ... pg_dump doesn't like
that, for no particularly good reason :-(. (This gratuitous failure
is gone in 7.3, but that doesn't help you much today.) I'd suggest
dropping and recreating the sequence, then using setval() to set its
current value correctly. Then you should be able to pg_dump.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Derek Neighbors 2002-09-28 17:06:07 pg_dumpall / restore issues
Previous Message Tom Lane 2002-09-28 03:24:33 Re: old db on a new system