Re: GUC flags

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: GUC flags
Date: 2021-12-09 08:17:54
Message-ID: YbG7sp+2YEYgbY0D@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 08, 2021 at 01:23:51PM +0100, Peter Eisentraut wrote:
> I wasn't really aware of this script either. But I think it's a good idea
> to have it. But only if it's run automatically as part of a test suite run.

Okay. If we do that, I am wondering whether it would be better to
rewrite this script in perl then, so as there is no need to worry
about the compatibility of grep. And also, it would make sense to
return a non-zero exit code if an incompatibility is found for the
automation part.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2021-12-09 08:42:56 Re: Make pg_waldump report replication origin ID, LSN, and timestamp.
Previous Message Thomas Munro 2021-12-09 08:16:57 Re: stat() vs ERROR_DELETE_PENDING, round N + 1