Inconsistent treatment of serials in pg_dump

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Inconsistent treatment of serials in pg_dump
Date: 2011-05-09 19:04:09
Message-ID: 4DC83AA9.2070409@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

All,

Just encountered this:

create table josh ( id serial not null, desc text );

pg_dump -Fc -T josh -f no_josh_dump postgres

pg_dump -Fc -t josh -f josh_dump postgres

pg_restore -d new no_josh_dump
pg_restore -d new josh_dump

pg_restore: [archiver (db)] Error from TOC entry 2645; 1259 49910
SEQUENCE josh_id_seq postgres
pg_restore: [archiver (db)] could not execute query: ERROR: relation
"josh_id_seq" already exists

It seems that if I exclude a table using -T, its dependant sequences do
not get excluded. But if I include it using -t, its dependent sequences
*do* get included.

Is there a reason this is a good idea, or is it just an oversight?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-05-09 19:31:15 Re: Why not install pgstattuple by default?
Previous Message Robert Haas 2011-05-09 19:00:17 Re: switch UNLOGGED to LOGGED