Re: psql - add SHOW_ALL_RESULTS option - pg_regress output - Mailing list pgsql-hackers

From Andres Freund
Subject Re: psql - add SHOW_ALL_RESULTS option - pg_regress output
Date
Msg-id 20220406020621.dfwvyuagy6tlc3fo@alap3.anarazel.de
Whole thread Raw
In response to Re: psql - add SHOW_ALL_RESULTS option  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: psql - add SHOW_ALL_RESULTS option - pg_regress output  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Hi,

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?

- Andres



pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: Logical replication row filtering and TOAST
Next
From: Andres Freund
Date:
Subject: Re: SQL/JSON: JSON_TABLE