Re: BUG #8154: pg_dump throws error beacause of field called "new".

From: Willy-Bas Loos <willybas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8154: pg_dump throws error beacause of field called "new".
Date: 2013-05-13 15:43:16
Message-ID: CAHnozThgBWkQ7XLgBqq7iTEMYDygzxO89+_diB2Vg3ZA2o4_Kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> willybas(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2013-05-13 19:53:02 Re: Odd Behavior After Multiple Deletes
Previous Message Heikki Linnakangas 2013-05-13 14:56:14 Re: Inconsistency between TO_CHAR() and TO_NUMBER()