Re: \connect case-folding change maybe not such a good idea - Mailing list pgsql-hackers

From Tom Lane
Subject Re: \connect case-folding change maybe not such a good idea
Date
Msg-id 9014.1014318605@sss.pgh.pa.us
Whole thread Raw
In response to \connect case-folding change maybe not such a good idea  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: \connect case-folding change maybe not such a good idea
List pgsql-hackers
I said:
> I think the wisest course may be to revert to the 7.1 \connect behavior

There is another possibility, which is to migrate to the new behavior
over time.  I like having pg_dump quote the names in \connect, because
that gives us a shot at working with names that have embedded spaces.
We could leave pg_dump as it stands in CVS tip, and modify psql to
work as follows:
    1. Quoted names in \connect are taken as quoted identifiers.
    2. Unquoted names are taken literally (not downcased).
Point 2 would allow forwards compatibility of existing dump files,
while point 1 makes the new pg_dump behavior work.  After a release
or two we could migrate to regular SQL-identifier handling in \connect.

This'd require a little bit of uglification in psql (another option_type
for scan_option()) but it doesn't seem too terribly awful.

Comments?

            regards, tom lane

pgsql-hackers by date:

Previous
From: Jean-Michel POURE
Date:
Subject: fmgr_info: function 20071: cache lookup failed
Next
From: Patrice Hédé
Date:
Subject: Re: UTF-8 data migration problem in Postgresql 7.2