Re: Hard-coded PUBLIC in pg_dump

From: "Nicolai Tufar" <ntufar(at)apb(dot)com(dot)tr>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hard-coded PUBLIC in pg_dump
Date: 2002-12-01 05:11:31
Message-ID: 006701c298f8$1cbe7370$8016a8c0@apb.com.tr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> ... but considering that SQL92 clearly lists it as
> a reserved word, there's not a lot of ground for that complaint to stand
> on.
>
> I'd prefer shifting PUBLIC back to the true-keyword category over any
> of the other workarounds you've suggested ...

It will work for me.
But why not change PUBLIC in pg_dump output to lower-case as well?

>
> regards, tom lane

Nic.

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joe Conway 2002-12-01 05:32:22 Re: Segmentation fault while COPY in 7.3
Previous Message Nicolai Tufar 2002-12-01 05:09:56 Re: Segmentation fault while COPY in 7.3

Browse pgsql-general by date

  From Date Subject
Next Message Joe Conway 2002-12-01 05:32:22 Re: Segmentation fault while COPY in 7.3
Previous Message Nicolai Tufar 2002-12-01 05:09:56 Re: Segmentation fault while COPY in 7.3

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2002-12-01 05:27:44 ALTER TABLE schema SCHEMA TO new_schema?
Previous Message Nicolai Tufar 2002-12-01 05:09:56 Re: Segmentation fault while COPY in 7.3