Re: Hard-coded PUBLIC in pg_dump

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nicolai Tufar <ntufar(at)apb(dot)com(dot)tr>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hard-coded PUBLIC in pg_dump
Date: 2002-12-01 19:04:21
Message-ID: 1038769460.72409.197.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

> > 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!

I believe these are fixed in the patch I sent in last week.

--
Rod Taylor <rbt(at)rbt(dot)ca>

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Rod Taylor 2002-12-01 19:04:22 Re: Hard-coded PUBLIC in pg_dump
Previous Message David Wheeler 2002-12-01 18:54:15 Re: Hard-coded PUBLIC in pg_dump

Browse pgsql-general by date

  From Date Subject
Next Message Rod Taylor 2002-12-01 19:04:22 Re: Hard-coded PUBLIC in pg_dump
Previous Message Tom Lane 2002-12-01 19:00:53 Re: Inserting large number of rows using libpq++ stops responding in c++

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2002-12-01 19:04:22 Re: Hard-coded PUBLIC in pg_dump
Previous Message David Wheeler 2002-12-01 18:54:15 Re: Hard-coded PUBLIC in pg_dump