Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-06 Thread Bruce Momjian
On Mon, Jan 2, 2017 at 01:25:35PM -0500, Robert Haas wrote: > > But, I can easily imagine a good number of people deciding they want > > mixed case on the server, and so quoting their identifiers. And, then > > deciding PostgreSQL is defective, rather than deciding their favorite > >

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-04 Thread Lewis, Ian (Microstar Laboratories)
Robert Haas [mailto:robertmh...@gmail.com] wrote: >> Where you get into trouble there is that you might run CREATE EXTENSION >> from that session Yes. I can see this problem. And, while I can imagine resolving it with context belonging to the extension, separate from the current session's

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-04 Thread Robert Haas
On Tue, Jan 3, 2017 at 6:45 PM, Lewis, Ian (Microstar Laboratories) wrote: > One idea, which would likely be harder to implement on the server, but > that would have less impact on third party tools and libraries, would be > to configure case folding on a session basis.

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-03 Thread Lewis, Ian (Microstar Laboratories)
Tom Lane [mailto:t...@sss.pgh.pa.us] wrote: >> 2. If the folding mode is chosen through a GUC variable, which >> is certainly what people would expect, then it turns out that >> it breaks client libraries/applications *anyway*, because an >> installation-wide setting could impose itself on a

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-03 Thread Tom Lane
"Lewis, Ian \(Microstar Laboratories\)" writes: > One idea, which would likely be harder to implement on the server, but > that would have less impact on third party tools and libraries, would be > to configure case folding on a session basis. There are a couple of problems

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-03 Thread Lewis, Ian (Microstar Laboratories)
Robert Haas [mailto:robertmh...@gmail.com] wrote: > The issue is, rather, that every extension written for > PostgreSQL, whether in or out of core, needs to handle this issue and > every general-purpose client tool (pgAdmin, etc.) needs to be aware of > it. I can see the accuracy of all of

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-03 Thread Jim Nasby
On 1/2/17 2:01 PM, Greg Stark wrote: The PostGIS extensions might not work on your system with different case rules if they haven't been 100% consistent with their camelCasing FWIW I've already run into a similar problem with inter-extension dependencies and relocatability. I've found hacks

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-03 Thread Alvaro Herrera
Lewis, Ian (Microstar Laboratories) wrote: > PS. To anyone who might know the answer: My Reply All to this group does > not seem to join to the original thread. All I am doing is Reply All > from Outlook. Is there something else I need to do to allow my responses > to join the original thread?

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-03 Thread Robert Haas
On Mon, Jan 2, 2017 at 8:03 PM, Lewis, Ian (Microstar Laboratories) wrote: > Personally, I believe such an option would increase, not decrease the > number of people who could relatively easily use PostgreSQL. If that is > right it is a strong argument for such a modal

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-02 Thread Lewis, Ian (Microstar Laboratories)
From: Robert Haas [mailto:robertmh...@gmail.com] wrote: > I'm not sure there's any way to split the baby here: tool authors will obviously prefer that PostgreSQL's behavior in this area be invariable, while people trying to develop portable database applications will prefer configurability. > As

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-02 Thread Lewis, Ian (Microstar Laboratories)
gsst...@gmail.com [mailto:gsst...@gmail.com] On Behalf Of Greg Stark wrote: > But the problem with configurable quoting rules is a bit different. > Imagine your application later decides to depend on PostGIS. So you load the PostGIS extension and perhaps also some useful functions you found on

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-02 Thread Greg Stark
On 25 December 2016 at 09:40, Lewis, Ian (Microstar Laboratories) wrote: > So, the current behavior already breaks many tools unless one accepts > that all symbols on the server are lower case. At root, based on reading > the threads you provided, this probably indicates

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-02 Thread Jim Nasby
On 1/2/17 12:25 PM, Robert Haas wrote: But, I can easily imagine a good number of people deciding they want mixed case on the server, and so quoting their identifiers. And, then deciding PostgreSQL is defective, rather than deciding their favorite administration or query tool is defective.

Re: [HACKERS] Cluster wide option to control symbol case folding

2017-01-02 Thread Robert Haas
On Sun, Dec 25, 2016 at 4:40 AM, Lewis, Ian (Microstar Laboratories) wrote: > I assume you are talking about general purpose tools that attempt to > interact with any database in any configuration. Obviously, a purpose > built tool, such as our own internal database

Re: [HACKERS] Cluster wide option to control symbol case folding

2016-12-25 Thread Craig Ringer
On 25 Dec. 2016 14:49, "Tom Lane" wrote: No. This has been looked into repeatedly in the past, and we simply don't want to deal with it. Quite aside from the impact on the server (which would be extensive), it would break every nontrivial application, and force them all

Re: [HACKERS] Cluster wide option to control symbol case folding

2016-12-25 Thread Lewis, Ian (Microstar Laboratories)
Tom Lane [mailto:t...@sss.pgh.pa.us] wrote: > Quite aside from the impact on the server (which would be extensive), it would break every nontrivial application, and force them all to try to deal with each possible folding behavior. I have read through the various threads related to this issue

Re: [HACKERS] Cluster wide option to control symbol case folding

2016-12-24 Thread Lewis, Ian (Microstar Laboratories)
On Saturday, December 24, 2016 10:49 PM Tom Lane [mailto:t...@sss.pgh.pa.us] wrote: > No. This has been looked into repeatedly in the past, and we simply don't want to deal with it. Fair enough. We will not pursue the issue then. That is why I asked. Ian Lewis (www.mstarlabs.com) -- Sent

Re: [HACKERS] Cluster wide option to control symbol case folding

2016-12-24 Thread Lewis, Ian (Microstar Laboratories)
On December 24, 2016 9:52 PM Craig Ringer [mailto:craig.rin...@2ndquadrant.com] wrote: > Personally I can see such an option being ok as an initdb-time setting or at CREATE DATABASE time. Case folding can know the current db from global context. > > It'd have to be fast though. Very fast. That

Re: [HACKERS] Cluster wide option to control symbol case folding

2016-12-24 Thread Tom Lane
"Lewis, Ian \(Microstar Laboratories\)" writes: > Is there any chance that the PostgreSQL developers would accept a new > cluster wide configuration option to control how the system handles > symbol case folding? No. This has been looked into repeatedly in the past, and

Re: [HACKERS] Cluster wide option to control symbol case folding

2016-12-24 Thread Craig Ringer
On 25 Dec. 2016 10:30 am, "Lewis, Ian (Microstar Laboratories)" < ile...@mstarlabs.com> wrote: Is there any chance that the PostgreSQL developers would accept a new cluster wide configuration option to control how the system handles symbol case folding? Probably not as a GUC (configuration

[HACKERS] Cluster wide option to control symbol case folding

2016-12-24 Thread Lewis, Ian (Microstar Laboratories)
Is there any chance that the PostgreSQL developers would accept a new cluster wide configuration option to control how the system handles symbol case folding? Currently PostgreSQL folds all un-quoted symbols to lower case. We would like to add a global configuration option with a name like