Re: Hard-coded PUBLIC in pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Nicolai Tufar <ntufar(at)apb(dot)com(dot)tr>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hard-coded PUBLIC in pg_dump
Date: 2002-12-01 18:51:26
Message-ID: 27206.1038768686@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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:

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.

regards, tom lane

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Bruce Momjian 2002-12-01 18:52:58 Re: Hard-coded PUBLIC in pg_dump
Previous Message Tom Lane 2002-12-01 18:49:30 Re: Hard-coded PUBLIC in pg_dump

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2002-12-01 18:52:58 Re: Hard-coded PUBLIC in pg_dump
Previous Message Tom Lane 2002-12-01 18:49:30 Re: Hard-coded PUBLIC in pg_dump

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-12-01 18:52:58 Re: Hard-coded PUBLIC in pg_dump
Previous Message Tom Lane 2002-12-01 18:49:30 Re: Hard-coded PUBLIC in pg_dump