| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange buildfarm failure on lionfish |
| Date: | 2007-07-25 21:29:29 |
| Message-ID: | 46A7C0B9.5060109@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark wrote:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
>
>> Someday we might like to allow this, but it seems to mean inventing a
>> new GUC context type, which I don't think I want to get into right now.
>>
>
> Another option would be adding an option to initdb to override default config
> settings in the postgreql.conf. Then the pg_regress could just specify options
> like this for the regression database if necessary.
>
>
>
I thought about that. But it makes things harder for the installcheck
case. I think the regression set needs to be able to run against a
pretty vanilla install (e.g. the only thing buildfarm specifies for
initdb is --no-locale ).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-07-25 21:38:51 | Re: strange buildfarm failure on lionfish |
| Previous Message | Andrew Dunstan | 2007-07-25 21:20:44 | Re: Machine available for community use |