From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Backpatching of "Teach the regular expression functions to do case-insensitive matching" |
Date: | 2011-05-09 14:56:20 |
Message-ID: | BANLkTike6Kg3cTYi21jsLMzZOHsh3tUugQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 9, 2011 at 10:39 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Well, since any problems in this are are going to bite us eventually
>> in 9.0+ even without any further action on our part, maybe it would be
>> wise to think up something we could add to the regression tests. That
>> would give us some immediate feedback from the buildfarm, and also
>> significantly improve the odds of someone compiling on a weird
>> platform noticing if things are broken.
>
> No objection here, but how will we do that? The regression tests are
> designed to work in any locale/encoding, and would become significantly
> less useful if they weren't.
I'm just shooting from the hip here, but maybe we could have a
separate (probably smaller) set of tests that are only designed to
work in a limited range of locales and/or encodings. I'm really
pleased that we now have the src/test/isolation stuff, and I think
some more auxilliary test suites would be quite excellent. Even if
people didn't always want to run every single one when doing things
manually, the buildfarm certainly could.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei Kaigai | 2011-05-09 14:57:30 | [v9.2] SECURITY LABEL on shared database object |
Previous Message | Robert Haas | 2011-05-09 14:53:56 | Re: Why not install pgstattuple by default? |