Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?)
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Amit Kapila <amit.kapila16@gmail.com>,
Kyotaro Horiguchi <horikyota.ntt@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-03-23T17:33:38Z
Lists: pgsql-hackers
Attachments
- v8-0001-Add-LOG-messages-when-replication-slots-become-ac.patch (application/octet-stream) patch v8-0001
On Thu, Mar 23, 2023 at 3:37 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > On 2023-Mar-22, Amit Kapila wrote: > > > I see that you have modified the patch to address the comments from > > Alvaro. Personally, I feel it would be better to add such a message at > > a centralized location instead of spreading these in different callers > > of slot acquire/release functionality to avoid getting these missed in > > the new callers in the future. However, if Alvaro and others think > > that the current style is better then we should go ahead and do it > > that way. I hope that we should be able to decide on this and get it > > into PG16. Anyone else would like to weigh in here? > > I like Peter Smith's suggestion downthread. +1. Please review the attached v8 patch further. -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Commits
-
Log messages for replication slot acquisition and release.
- 7c3fb505b14e 17.0 landed