Re: pgsql: Add TAP test to automate the equivalent of check_guc

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christoph Berg <myon(at)debian(dot)org>
Cc: 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-12 16:50:00
Message-ID: 2282966.1644684600@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Christoph Berg <myon(at)debian(dot)org> writes:
> I was confusing that with this: The problem that led to the pg_config
> patch years ago was that we have a /usr/bin/pg_config in
> (non-major-version-dependant) libpq-dev, and
> /usr/lib/postgresql/NN/bin/pg_config in the individual
> postgresql-server-dev-NN packages, and iirc the /usr/bin version
> didn't particularly like the other binaries being in
> /usr/lib/postgresql/NN/bin/.

Ah. That seems a bit problematic anyway ... if the version-dependent
pg_configs don't all return identical results, what's the
non-version-dependent one supposed to do?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Christoph Berg 2022-02-12 17:40:06 Re: pgsql: Add TAP test to automate the equivalent of check_guc
Previous Message Christoph Berg 2022-02-12 16:31:55 Re: pgsql: Add TAP test to automate the equivalent of check_guc

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-02-12 17:25:03 Re: Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates
Previous Message Tom Lane 2022-02-12 16:47:20 Re: Why is src/test/modules/committs/t/002_standby.pl flaky?