| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Should pg_upgrade use --quote-all-identifiers? |
| Date: | 2013-05-01 01:28:59 |
| Message-ID: | CAM-w4HMYcgj6gB=i8zU7_Tu392eCXqc9A8hqRySfaV=5LOYEvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 1, 2013 at 2:23 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Well, readability of those commands is worth something too, but in any
> case the short answer is that pg_dump has only one quote-an-identifier
> function, not different ones for server commands and final output.
Well for the final output one reason it's nice not to quote is that it
makes it easier to use the SQL generated by --inserts on a
non-postgres database. Mainly I'm thinking of the case issue but also
some databases use strange quoting rules.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-05-01 02:14:42 | Re: pgsql: Add regression test for bug fixed by recent refactoring. |
| Previous Message | Tom Lane | 2013-05-01 01:23:09 | Re: Should pg_upgrade use --quote-all-identifiers? |