Re: [Proposal] Adding Log File Capability to pg_createsubscriber

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Gyan Sreejith <gyan(dot)sreejith(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Smith <smithpb2250(at)gmail(dot)com>
Subject: Re: [Proposal] Adding Log File Capability to pg_createsubscriber
Date: 2026-03-17 10:40:53
Message-ID: CAA4eK1Kxs9-fyewpvasgJ=Wrw_h+j6GBHNcNfoJ47mv7+L9N_A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 17, 2026 at 11:36 AM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> 1)
> I observed that when we give both --verbose and --logdir options, it
> skips verbose and only dumps logs to logdir. Is this intentional?
>
> I don't see any other postgres command with both the options provided
> and thus cannot compare the behaviour. But IMO, if the user has
> explicitly given both options, we should dump the log on both (stdout
> and logfile).
>

The entire log should be dumped in the specified log_file. I think
this is similar to one setting server's log_level to debug1 and then
start server with -l option in which case the entire log is dumped to
server log file.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilia Evdokimov 2026-03-17 10:50:59 Re: Reduce planning time for large NOT IN lists containing NULL
Previous Message Alberto Piai 2026-03-17 10:31:47 Adding a stored generated column without long-lived locks