BUG #8443: duplicated oids after dump
The following bug has been logged on the website:
Bug reference: 8443
Logged by: Bartłomiej Rychtarski
Email address: b.rychtarski@teb-akademia.pl
PostgreSQL version: 9.2.4
Operating system: debian
Description:
executed full dump of database without oids:
pg_dump -v -a -E UTF8 --disable-dollar-quoting --disable-triggers
after restoring database from dump in each table there are rows with
duplicated oids
problem applies to about 2% of rows in each table
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 2013-09-11 12:07:25 +0000, b.rychtarski@teb-akademia.pl wrote:
executed full dump of database without oids:
pg_dump -v -a -E UTF8 --disable-dollar-quoting --disable-triggersafter restoring database from dump in each table there are rows with
duplicated oids
So, just to make sure I understand you correctly: You dumped a database
in a form that doesn't contain oids, loaded it into a new one where the
preexisting schema uses oids in user tables? After loading that data
there were duplicate oids?
* Do you have a unique constraint over the oid columns?
* Was there any preexisting data?
* Were there any concurrent inserts?
* Are the "duplicates" rows in the same relation or in different ones?
* How many records do exist in the restore you made?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs