Re: TRUE/FALSE vs true/false - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: TRUE/FALSE vs true/false
Date
Msg-id 20120816193216.GB6286@momjian.us
Whole thread Raw
In response to Re: TRUE/FALSE vs true/false  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: TRUE/FALSE vs true/false
List pgsql-hackers
On Thu, Aug 16, 2012 at 02:21:12PM -0500, Kevin Grittner wrote:
> Bruce Momjian <bruce@momjian.us> wrote:
>  
> > So what do we want to do with this?  I am a little concerned that
> > we are sacrificing code clarity for backpatching ease, but I don't
> > do as much backpatching as Tom.
>  
> Well, if you back-patched this change, it would eliminate the issue
> for Tom, wouldn't it?  Not sure if that's sane; just a thought.

I would be worried about some instability in backpatching.  I was
looking for an 'ignore-case' mode to patch, but I don't see it.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: TRUE/FALSE vs true/false
Next
From: Josh Berkus
Date:
Subject: Re: Planner avoidance of index only scans for partial indexes