Re: psql - add SHOW_ALL_RESULTS option - pg_regress output

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: psql - add SHOW_ALL_RESULTS option - pg_regress output
Date: 2022-04-06 08:37:29
Message-ID: 4d6c4e64-b4e5-e050-23f9-e960df8f434b@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.04.22 04:06, Andres Freund wrote:
> On 2022-04-04 23:32:50 +0200, Peter Eisentraut wrote:
>> This has been committed.
>
> It's somewhat annoying that made pg_regress even more verbose than before:
>
> ============== removing existing temp instance ==============
> ============== creating temporary instance ==============
> ============== initializing database system ==============
> ============== starting postmaster ==============
> running on port 51696 with PID 2203449
> ============== creating database "regression" ==============
> CREATE DATABASE
> ALTER DATABASE
> ALTER DATABASE
> ALTER DATABASE
> ALTER DATABASE
> ALTER DATABASE
> ALTER DATABASE
> ============== running regression test queries ==============
>
> Unfortunately it appears that neither can CREATE DATABASE set GUCs, nor can
> ALTER DATABASE set multiple GUCs in one statement.
>
> Perhaps we can just set SHOW_ALL_RESULTS off for that psql command?

Do you mean the extra "ALTER DATABASE" lines? Couldn't we just turn all
of those off? AFAICT, no one likes them.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-04-06 08:45:12 Re: pg_walinspect - a new extension to get raw WAL data and WAL stats
Previous Message Amit Kapila 2022-04-06 08:31:35 Re: Logical replication timeout problem