| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: TRUE/FALSE vs true/false |
| Date: | 2012-08-16 19:32:16 |
| Message-ID: | 20120816193216.GB6286@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 16, 2012 at 02:21:12PM -0500, Kevin Grittner wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2012-08-16 20:02:26 | Re: Planner avoidance of index only scans for partial indexes |
| Previous Message | Kevin Grittner | 2012-08-16 19:21:12 | Re: TRUE/FALSE vs true/false |