Re: Hard-coded PUBLIC in pg_dump

From: David Wheeler <david(at)wheeler(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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:54:15
Message-ID: 49D4448A-055E-11D7-8D38-0003931A964A@wheeler.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

On Sunday, December 1, 2002, at 10:49 AM, Tom Lane wrote:

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> PUBLIC doesn't seem like a very common column name --- seems safe to
>> make it reserved. We made 'value' reserved in 7.3, and that was a
>> much
>> more common one.
>
> I'm still quite unhappy about 'value', and would like to look into
> making it unreserved again. This business does show that there are
> some
> pitfalls in that, though :-(

Actually, I don't think it's reserved in 7.3, only in the 7.4
development sources. Otherwise, Bricolage would fail hard, and it
doesn't. So there's some time to play with this issue, I think.

David

--
David Wheeler AIM: dwTheory
david(at)wheeler(dot)net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory(at)jabber(dot)org

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Rod Taylor 2002-12-01 19:04:21 Re: Hard-coded PUBLIC in pg_dump
Previous Message Bruce Momjian 2002-12-01 18:52:58 Re: Hard-coded PUBLIC in pg_dump

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-12-01 19:00:53 Re: Inserting large number of rows using libpq++ stops responding in c++
Previous Message Bruce Momjian 2002-12-01 18:52:58 Re: Hard-coded PUBLIC in pg_dump

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2002-12-01 19:04:21 Re: Hard-coded PUBLIC in pg_dump
Previous Message Bruce Momjian 2002-12-01 18:52:58 Re: Hard-coded PUBLIC in pg_dump