Josh Berkus wrote: > Severity: normal > > Versions tested: 9.0.4 and 9.1.1 > Installed from packages on Ubuntu > > Reproduceability: 100% on this server > have not tried a test case yet > > Steps: > > 1. large running 8.4.8 PostgreSQL database > > 2. /usr/lib/postgresql/9.1/bin/pg_dump -Fc -v -f test.dump dbname > > 3. dumps all table etc definitions correctly. then: > > pg_dump: saving database definition > pg_dump: SQL command failed > pg_dump: Error message from server: ERROR: NEW used in query that is > not in a rule > LINE 1: ...END AS min_value, cache_value, is_cycled, is_called from new > ^ > pg_dump: The command was: SELECT sequence_name, start_value, last_value, > increment_by, CASE WHEN increment_by > 0 AND max_value = > 9223372036854775807 THEN NULL WHEN increment_by < 0 AND max_value = > -1 THEN NULL ELSE max_value END AS max_value, CASE WHEN > increment_by > 0 AND min_value = 1 THEN NULL WHEN increment_by < 0 > AND min_value = -9223372036854775807 THEN NULL ELSE min_value END > AS min_value, cache_value, is_cycled, is_called from new > > (yes, that is the entire query, I checked the logs) > > ... somehow the query to dump the sequences is getting mangled. Any > clue how?
Seems you have a sequence called "new"; seems we don't handle that well. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
