Re: BUG #8154: pg_dump throws error beacause of field called "new". - Mailing list pgsql-bugs

From Willy-Bas Loos
Subject Re: BUG #8154: pg_dump throws error beacause of field called "new".
Date
Msg-id CAHnozThgBWkQ7XLgBqq7iTEMYDygzxO89+_diB2Vg3ZA2o4_Kw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #8154: pg_dump throws error beacause of field called "new".  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #8154: pg_dump throws error beacause of field called "new".  (Willy-Bas Loos <willybas@gmail.com>)
List pgsql-bugs
oh, silly me.
I was making a dump of a  PostgreSQL 8.4.17 backend with pg_dump
(PostgreSQL) 9.1.9


On Mon, May 13, 2013 at 4:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> willybas@gmail.com writes:
> > pg_dump (PostgreSQL) 9.1.9 ends in an error when backing up my db, which
> > contains a field called "new".
>
> Works for me:
>
> regression=# create table new (f1 text, new text);
> CREATE TABLE
> regression=# insert into new (f1, new) values ('1','2');
> INSERT 0 1
> regression=# copy new(f1,new) to stdout;
> 1       2
>
> You sure the server is 9.1?
>
>                         regards, tom lane
>



--
"Quality comes from focus and clarity of purpose" -- Mark Shuttleworth

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Inconsistency between TO_CHAR() and TO_NUMBER()
Next
From: antreimer@gmail.com
Date:
Subject: BUG #8151: client libraries not working on mingw-w64 gcc 4.8