From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: !USE_WIDE_UPPER_LOWER compile errors in v10+ |
Date: | 2017-09-22 03:08:04 |
Message-ID: | 20170922030804.GB204855@rfd.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 21, 2017 at 05:38:13PM -0400, Tom Lane wrote:
> I wrote:
> > Noah Misch <noah(at)leadboat(dot)com> writes:
> >> Perhaps it is time to require HAVE_WCSTOMBS and HAVE_TOWLOWER, removing
> >> USE_WIDE_UPPER_LOWER? Every buildfarm fossil has both.
>
> > +1 ... if nothing else, there's the problem that untested code is likely
> > to be broken. You just proved it *is* broken, of course, but my point
> > is that even if we repaired the immediate damage we could have little
> > confidence in it staying fixed.
That would be easy enough to ensure by adding ac_cv_func_towlower=no to some
buildfarm animal. But the real-world need for said code is clearly dead and
gone. Good riddance.
> Meanwhile, I see that Peter has posted a fix for the immediate problem.
> I propose that Peter should apply his fix in HEAD and v10, and then
> I'll rip out the !USE_WIDE_UPPER_LOWER code paths in HEAD only.
That works for me.
From | Date | Subject | |
---|---|---|---|
Next Message | Schneider | 2017-09-22 04:52:12 | Re: Generate wait event list and docs from text file |
Previous Message | Michael Paquier | 2017-09-22 02:54:57 | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |