Re: Hard-coded PUBLIC in pg_dump - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Hard-coded PUBLIC in pg_dump
Date
Msg-id 200212011852.gB1Iqw023554@candle.pha.pa.us
Whole thread Raw
In response to Re: Hard-coded PUBLIC in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Hard-coded PUBLIC in pg_dump
Re: Hard-coded PUBLIC in pg_dump
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > We made 'value' reserved in 7.3, and that was a much
> > more common one.
> 
> BTW, you mean "current" not "7.3".  That patch has still got some
> serious problems anyway:

Yes, I realized later it was current. I was fixing the dbdpg regression
tests, and git bitten by that, and forgot I was using current and not
7.3.

> 
> 7.3:
> 
> regression=# select value;
> ERROR:  Attribute "value" not found
> 
> HEAD:
> 
> regression=# select value;
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.

Yow!

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Hard-coded PUBLIC in pg_dump
Next
From: David Wheeler
Date:
Subject: Re: Hard-coded PUBLIC in pg_dump