From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Christoph Berg <myon(at)debian(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Add TAP test to automate the equivalent of check_guc |
Date: | 2022-02-11 15:41:27 |
Message-ID: | 2027230.1644594087@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> On Fri, Feb 11, 2022 at 09:59:55AM -0500, Tom Lane wrote:
>> This seems like a pretty bad idea even if it weren't failing outright.
>> We should be examining the version of the file that's in the source
>> tree; the one in the installation tree might have version-skew
>> problems, if you've not yet done "make install".
> My original way used the source tree, but Michael thought it would be an issue
> for "installcheck" where the config may not be available.
Yeah, you are at risk either way, but in practice nobody is going to be
running these TAP tests without a source tree.
> This is what I had written:
> FROM (SELECT regexp_split_to_table(pg_read_file('postgresql.conf'), '\n') AS ln) conf
That's not using the source tree either, but the copy in the
cluster-under-test. I'd fear it to be unstable in the buildfarm, where
animals can append whatever they please to the config file being used by
tests.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2022-02-11 17:29:29 | Re: pgsql: Add TAP test to automate the equivalent of check_guc |
Previous Message | Justin Pryzby | 2022-02-11 15:35:49 | Re: pgsql: Add TAP test to automate the equivalent of check_guc |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-02-11 15:50:09 | Re: refactoring basebackup.c |
Previous Message | Tom Lane | 2022-02-11 15:36:14 | Re: OpenSSL conflicts with wincrypt.h |