| 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:49:30 |
| Message-ID: | 27169.1038768570@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:
> 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 :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-12-01 18:51:26 | Re: Hard-coded PUBLIC in pg_dump |
| Previous Message | Bruce Momjian | 2002-12-01 18:44:06 | Re: Hard-coded PUBLIC in pg_dump |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-12-01 18:51:26 | Re: Hard-coded PUBLIC in pg_dump |
| Previous Message | Bruce Momjian | 2002-12-01 18:44:06 | Re: Hard-coded PUBLIC in pg_dump |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-12-01 18:51:26 | Re: Hard-coded PUBLIC in pg_dump |
| Previous Message | Bruce Momjian | 2002-12-01 18:44:06 | Re: Hard-coded PUBLIC in pg_dump |