On Thu, Aug 18, 2016 at 04:49:04PM -0400, Bruce Momjian wrote:
> On Thu, Aug 18, 2016 at 03:01:48PM -0400, Peter Eisentraut wrote:
> > On 8/18/16 1:59 PM, Bruce Momjian wrote:
> > > o compares words in columns that can only support keywords as
> > > case-insensitive, double-quoted or not
> > >
>
On Thu, Aug 18, 2016 at 03:01:48PM -0400, Peter Eisentraut wrote:
> On 8/18/16 1:59 PM, Bruce Momjian wrote:
> > o compares words in columns that can only support keywords as
> > case-insensitive, double-quoted or not
> >
> > o compares words in columns that can contain user/db names or keywords
On 8/18/16 1:59 PM, Bruce Momjian wrote:
> o compares words in columns that can only support keywords as
> case-insensitive, double-quoted or not
>
> o compares words in columns that can contain user/db names or keywords
> as case-sensitive if double-quoted, case-insensitive if not
I can maybe
Bruce Momjian writes:
> On Thu, Aug 18, 2016 at 02:06:39PM -0400, Tom Lane wrote:
>> Is there really enough demand for this to justify subtle breakage
>> of existing pg_hba.conf entries? It'd probably have been fine if
>> we did it like that originally, but I think it's a bit late now.
> Well, i
On Thu, Aug 18, 2016 at 02:06:39PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I was looking at this TODO item from 2009:
> > https://www.postgresql.org/message-id/4AA7B197.70002%40usit.uio.no
> > I have implemented this in the attached patch. It does two things:
>
> Is there really e
Bruce Momjian writes:
> I was looking at this TODO item from 2009:
> https://www.postgresql.org/message-id/4AA7B197.70002%40usit.uio.no
> I have implemented this in the attached patch. It does two things:
Is there really enough demand for this to justify subtle breakage
of existing pg_hba.
