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

From Nicolai Tufar
Subject Re: Hard-coded PUBLIC in pg_dump
Date
Msg-id 006701c298f8$1cbe7370$8016a8c0@apb.com.tr
Whole thread Raw
In response to Hard-coded PUBLIC in pg_dump  (Nicolai Tufar <ntufar@apb.com.tr>)
List pgsql-hackers
----- Original Message ----- 
From: "Tom Lane" <tgl@sss.pgh.pa.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.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Odd optimiser behaviour
Next
From: Joe Conway
Date:
Subject: ALTER TABLE schema SCHEMA TO new_schema?