Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore

From: Steve Purcell <steve(at)sanityinc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
Date: 2009-07-05 16:37:35
Message-ID: 824E8CE3-2F90-4169-9B9C-BE1E5AF87EA6@sanityinc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks for the quick reply, Tom. That makes sense, and yes, that does
appear to be the problem.

I thought that I *was* using the newer pg_dump, but I'm doing this on
Debian:

# su - postgres -c "env PGCLUSTER=8.3/main pg_dump openx|env
PGCLUSTER=8.4/main pg_restore -d template1 -C"

And the debian pg_wrapper script ends up selecting the 8.3 pg_dump
binary in the first case. I'll have to figure out if there's even a
way to execute the newer pg_dump against the old database, which I
expect to be fiddly.

Thanks again, and sorry for the noise.

-Steve

On 5 Jul 2009, at 17:55, Tom Lane wrote:

> "Steve Purcell" <steve(at)sanityinc(dot)com> writes:
>> The DB schema for openx (openx.org) contains a table with a column
>> called
>> "window", which now causes a syntax error if unquoted. pg_dump
>> doesn't
>> quote the column, so pg_restore/psql fail on the pg_dump output.
>
> This is one of the reasons why it's recommended that you use the later
> version's pg_dump to perform a cross-version dump and restore. 8.4's
> pg_dump knows that "window" is a reserved word, but 8.3's could hardly
> be expected to.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marko Tiikkaja 2009-07-05 19:27:47 BUG #4902: Subquery in VALUES referencing a CTE
Previous Message Tom Lane 2009-07-05 16:18:39 Re: Diffrent column ordering after dump/restore tables with INHERITS