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

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
Date: 2009-07-06 11:31:21
Message-ID: h2sna9$ur7$1@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2009-07-05, Steve Purcell <steve(at)sanityinc(dot)com> wrote:
> 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.

easiest is to bypass pg_wrapper

/usr/lib/postgresql/8.4/bin/pg_dump -p 5432

I have raised this with debian.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Wojciech Strzałka 2009-07-06 12:16:11 Re: Unknown winsock error 10061
Previous Message Dave Page 2009-07-06 11:26:38 Re: Unknown winsock error 10061