On Fri, Dec 2, 2011 at 4:48 AM, <h...@alkheme.com> wrote: > The following bug has been logged on the website: > > Bug reference: 6317 > Logged by: hua ming fei > Email address: h...@alkheme.com > PostgreSQL version: 9.0.1 > Operating system: Centos 5.5 > Description: > > use pg_dump when didn't close the application , weird things occured . the > current value of one sequence is more slower than the max number of one > primary key base on the sequence . So, I looked into the dump file , found > command" > SELECT pg_catalog.setval('attrnamemaster_attrnameid_seq', 3009, > true);" to > set sequence values number , but the import data, there are many lines with > number larger than the sequence value : > 3012 38 2147483647 t 10041 material material > material 1004.10041 4.1 f > 3013 38 2147483647 t 10042 disable > 1004.10042 4.2 f
Without a reproducible test case, it's tough to see how anyone's going to be able to fix any bug that may be lurking here. When you use vague phrases like "when didn't close the application, weird things occurred", it's kind of hard to figure out what exactly you did. If you come up with a specific sequence of steps involving simple tools like pg_dump and psql that produces a result you think is wrong, someone here can probably (a) tell you whether the behavior is intended, and (b) if not, fix it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
