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
context
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 client
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 th
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 f
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 Sta
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 that
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 vi
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 s
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
sy
