Re: "Unified logging system" breaks access to pg_dump debug outputs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: "Unified logging system" breaks access to pg_dump debug outputs
Date: 2020-09-17 16:53:38
Message-ID: 222834.1600361618@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2020-Sep-15, Tom Lane wrote:
>> After further thought, I concluded that's a clearly superior solution,
>> so 0001 attached does it like that. After noting that the enum values
>> are in the opposite direction from how I thought they went, I realized
>> that "increase_level" might be a bit ambiguous, so I now propose to
>> call it pg_logging_increase_verbosity.

> I like this better too ... I've wished for extra-verbose messages from
> pg_dump in the past, and this now allows me to add something should I
> want them again.

Pushed, thanks for reviewing.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2020-09-17 17:12:12 Planner, check if can use consider HASH for groupings (src/backend/optimizer/plan/planner.c)
Previous Message Fujii Masao 2020-09-17 16:50:00 Re: Retry Cached Remote Connections for postgres_fdw in case remote backend gets killed/goes away