Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
Date
Msg-id 1275687432-sup-8900@alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
List 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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: superuser unable to modify settings of a system table
Next
From: "Kevin Grittner"
Date:
Subject: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail