Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVeno-00620v-16 for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Dec 2025 23:50:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vVenn-0095Nq-0v for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Dec 2025 23:50:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVenm-0095Ni-31 for pgsql-hackers@lists.postgresql.org; Tue, 16 Dec 2025 23:49:59 +0000 Received: from mail-qt1-x82a.google.com ([2607:f8b0:4864:20::82a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vVenk-00189J-37 for pgsql-hackers@lists.postgresql.org; Tue, 16 Dec 2025 23:49:59 +0000 Received: by mail-qt1-x82a.google.com with SMTP id d75a77b69052e-4ee1e18fb37so52427421cf.0 for ; Tue, 16 Dec 2025 15:49:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1765928995; x=1766533795; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=reYWJzZTXuR4FKwLrZtn8Z6i/xS5X17de/pwYoMYpiI=; b=FPNXh4p2QZfr+kALs5qLN+fRdUQ8HBau/qvyVFpyrBscAgXzKSLqojgS4fuzYJdEM5 HMGzE0W9vpfSBl0UYocCOfps9JXV3DCToAxHGeh3P7fTDVSAsh9gSZxXytiwFOQ5Ogco 9kL+knQyPCaz2MELJPe6JNvncol1p+iCSRR1rA5sqeZKBucBKFfKN6ZPZgkK08TGqG4u /ch7exLrSsDEmLLeagPvGfOKqyGO1V6XcXzTysBDERNHTx1CpUd5xcFHG39APaUJY/YB +3hps0jnlmMm2mMJSvRCw22zrCnP1tga3B94VEECyJLLipXmTGswuu1T5NIAN4dC0WuH VvOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1765928995; x=1766533795; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=reYWJzZTXuR4FKwLrZtn8Z6i/xS5X17de/pwYoMYpiI=; b=FX6bIZSkStBwB2jnT2nJbr512Jtbpm4GQXyOZvYfCMve9dJf0boxMaenAiENqNcOOJ d+sP1chYWm40a1uPVVQouDSxaJ8nUIY/E5FeYNgMmZ2MguB/XfAk3FhrigOWJDgZutKY Ddm9vYktaNv0R4PxzVc+zo3ecmyfFIsJfXOj+jBtqY9JxVvIb7NBlKBVXMNw9RgEPHmj SYnOejggVKIqd+hDpepQzoqCQc7MXBqLT3FCV9/wh64A9hUDs12/ZiX8vc56qEEF3TGP 5gEv+9pfC6BmJAO4ePDoVnr8ChnHI/PBuPxZnakeJms3qctNRI2DRYqlKoFsPK9Yr8jy B7ng== X-Gm-Message-State: AOJu0YwOR9pIHyk1SzfF9ojcjBY48AC/DaM/7n3J1U8i9XfXIAyFMNx8 8/JOYs15blFzCx7s1pitlJr89t8mzCU1R9EFjl14JjBg6KprmiwgBqGHf5jWv7FUhyFqJLjf2ZL 7vb3Zig5nzlWBU6cEaSLE0xDj7wjCRlo= X-Gm-Gg: AY/fxX70bKvol/wqs+65foW/+k97UAr70JGRibsih74KBOWkeIDk+uiiDrvAR8th5rC utfatc6PGiZJ/G6mKVADZDXlg2T3rOfwt4MhjAkZLFVTyvvRvL1fksBLVrQyfl4lM0Ut6Z9bjDd xlvG8YmsZsVxImq3tcwrJDZTEZa767imXbhBDaRn8cj3zvXpbIpUv86lS99q0EKi1GQVF/x2/cX rM27fBKezasRB5lxEvLqjlBPpLo8tBCc9J4pca/qT6l0+WdECGbhxidlg57e30Ktt9oaqt9O6YV Ng3SaCdVOTyAoq05vSue2xM7v3FD X-Google-Smtp-Source: AGHT+IETf88+Imlzfuwril5d4Na8Lk0ieD6Lv7P+JSTwoTq5uql7d4Eo9fEk2Kvv8F+bNJGIs+msGWSfazAOpxROAtc= X-Received: by 2002:a05:622a:4112:b0:4f1:b1f5:277b with SMTP id d75a77b69052e-4f1d04b1db6mr231608251cf.23.1765928994898; Tue, 16 Dec 2025 15:49:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Peter Smith Date: Wed, 17 Dec 2025 10:49:28 +1100 X-Gm-Features: AQt7F2o-K87uUIN1jdy4DTqlCVNxiXLhd9LhIEgyEATURra9HI8CMDhgNggHkPo Message-ID: Subject: Re: [Proposal] Adding Log File Capability to pg_createsubscriber To: Gyan Sreejith Cc: pgsql-hackers@lists.postgresql.org, vignesh C Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Dec 12, 2025 at 12:33=E2=80=AFPM Gyan Sreejith wrote: > > Thanks for the feedback, Peter. > > I am currently working on the SGML docs update, and will promptly get bac= k with an update. > > For your second point, currently, all output goes directly to the console= . I thought it made more sense to break it up into multiple files depending= on what was being invoked. Do you have another opinion? > The point I was trying to make was that if you are going to have a "--logdir" option, then IMO that option should do nothing other than change the destination for the logs. In other words, current behaviour is effectively --logdir=3Dconsole, so --logdir=3Dsome_other_folder should not have some side-effect causing the log to get split into multiple files. If you want to split logs, then I thought Kuroda-San's suggestion [1] sounded better --- (a) mimic pg_upgrade more closely and (b) reconsider if -logdir is needed at all. =3D=3D=3D=3D=3D=3D [1] https://www.postgresql.org/message-id/OSCPR01MB14966FD0961F512B29BD46D6= BF5AAA%40OSCPR01MB14966.jpnprd01.prod.outlook.com Kind Regards, Peter Smith. Fujitsu Australia