| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)postgresql(dot)org>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| Date: | 2007-06-26 15:31:31 |
| Message-ID: | 46813153.10908@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Gregory Stark wrote:
> It may still be worth telling one version of Postgres about anticipated
> keywords prior to a release which adds them so that people who don't follow
> instructions and try a dump generated with an old pg_dump have a fighting
> chance. Besides, what's a person to do if they have a dump lying around?
> Restore it in an old database so they can re-dump it with the new pg_dump?
>
>
That is in fact the only thing we fairly much guarantee to work.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-06-26 15:45:51 | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| Previous Message | Gregory Stark | 2007-06-26 15:15:07 | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-06-26 15:45:51 | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| Previous Message | Gregory Stark | 2007-06-26 15:15:07 | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |