| 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:07:27 |
| Message-ID: | CAM-w4HMC3n03DhoV9LEQa+4YHudNy3v8vYw1HpDDUekKeUTAsA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 1, 2013 at 12:55 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Seems like this might be a good idea to avoid the type of failure
> exhibited in bug #8128. We don't care too much about the readability
> of the dump script created during an upgrade, so it's hard to see a
> downside.
Huh. I thought you were talking about quoting identifiers in an SQL
dump. But you're not, you're talking about quoting identifiers in sql
being sent to the server during the pg_dump process. Why did pg_dump
ever not quote all such identifiers?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2013-05-01 01:23:03 | Re: Remaining beta blockers |
| Previous Message | Tom Lane | 2013-04-30 23:55:33 | Should pg_upgrade use --quote-all-identifiers? |