Re: [Proposal] Adding Log File Capability to pg_createsubscriber

Euler Taveira <euler@eulerto.com>

From: "Euler Taveira" <euler@eulerto.com>

To: "vignesh C" <vignesh21@gmail.com>, "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>

Cc: "Gyan Sreejith" <gyan.sreejith@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, "Peter Smith" <smithpb2250@gmail.com>

Date: 2025-12-18T01:28:54Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

pg_createsubscriber: Don't use MAXPGPATH
- 99b726ac4894 19 (unreleased) landed
pg_createsubscriber: Remove separate logfile_open() function
- f5528b90b411 19 (unreleased) landed
pg_createsubscriber: Use logging.c log file callback
- 847336ba53af 19 (unreleased) landed
Add log file support to logging.c
- 41237556f8c5 19 (unreleased) landed
pg_createsubscriber: Add -l/--logdir option to redirect output to files.
- 6b5b7eae3ae6 19 (unreleased) landed
pg_createsubscriber: Introduce module-specific logging functions.
- d6628a5ea0a5 19 (unreleased) landed

On Wed, Dec 17, 2025, at 7:07 AM, vignesh C wrote:
>
> By providing this as an option, users can store the log files outside
> the data directory, eliminating the need for any additional handling
> during backups.
>

Do we really need an option to capture the stdout / stderr output to a file? I
doubt it. There is already various ways to capture. psql and pg_upgrade are the
only tools that have this option. And honestly, I've never seen these options
used in the field.

-- 
Euler Taveira
EDB   https://www.enterprisedb.com/