On 15.11.2011 02:43, Josh Berkus wrote:
... 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.
So, tested this some more. For some reason, 8.4's pg_dump would
recognize NEW as a reserved word
The following bug has been logged online:
Bug reference: 6293
Logged by: Teun Hoogendoorn
Email address: t...@atsc.nl
PostgreSQL version: 9.1
Operating system: Linux
Description:JDBC driver performance
Details:
Using the postgresql-9.1-901.jdbc3.jar driver instead o
On 2011-11-15 v46 01.43, Josh Berkus wrote:
... 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.
So, tested this some more. For some reason, 8.4's pg_dump would
recognize NEW as a reserved word
On Tue, Nov 15, 2011 at 5:16 AM, Heikki Linnakangas
wrote:
> NEW used to be a reserved keyword, but it's not so in 9.0 anymore. So 9.0
> pg_dump thinks it doesn't need to be quoted.
Why isn't it correct?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
The following bug has been logged online:
Bug reference: 6294
Logged by: CN Liu
Email address: cnli...@fastmail.fm
PostgreSQL version: 9.1.1
Operating system: Debian Squeeze
Description:character 0xefbd9e of encoding "UTF8" has no equivalent
in "BIG5"
Details:
Howev
Robert Haas writes:
> On Tue, Nov 15, 2011 at 5:16 AM, Heikki Linnakangas
> wrote:
>> NEW used to be a reserved keyword, but it's not so in 9.0 anymore. So 9.0
>> pg_dump thinks it doesn't need to be quoted.
> Why isn't it correct?
It's correct to not quote it in pg_dump's output (since we make
Hello, Tom.
You wrote:
TL> Robert Haas writes:
>> On Tue, Nov 15, 2011 at 5:16 AM, Heikki Linnakangas
>> wrote:
>>> NEW used to be a reserved keyword, but it's not so in 9.0 anymore. So 9.0
>>> pg_dump thinks it doesn't need to be quoted.
>> Why isn't it correct?
TL> It's correct to not quote
