| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov> |
| Cc: | Hartmut Goebel <h(dot)goebel(at)goebel-consult(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
| Date: | 2010-06-04 21:38:53 |
| Message-ID: | 1275687432-sup-8900@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Excerpts from Kevin Grittner's message of vie jun 04 14:53:17 -0400 2010:
> Same here. I suspect that this is much more commonn than many
> PostgreSQL developers realize; and I think it makes a reasonable
> case for at least an *option* to quote all identifiers emitted by
> pg_dump.
I don't think "dumps must be human-readable" is an argument to reject
such a switch, as long as it's off by default. And I haven't seen any
other valid argument either, so +1 from me.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-06-04 21:40:05 | Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail |
| Previous Message | Tom Lane | 2010-06-04 21:13:34 | Re: superuser unable to modify settings of a system table |