Re: Replication slot stats misgivings
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Date: 2021-04-27T03:28:12Z
Lists: pgsql-hackers
On Tue, Apr 27, 2021 at 11:45 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Tue, Apr 27, 2021 at 8:01 AM vignesh C <vignesh21@gmail.com> wrote: > > > > On Mon, Apr 26, 2021 at 8:42 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > > On Mon, Apr 26, 2021 at 8:01 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > > > > > > > On Fri, Apr 23, 2021 at 6:15 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > > > > > > On Mon, Apr 19, 2021 at 4:28 PM vignesh C <vignesh21@gmail.com> wrote: > > > > > > > > > > > > I have made the changes to update the replication statistics at > > > > > > replication slot release. Please find the patch attached for the same. > > > > > > Thoughts? > > > > > > > > > > > > > > > > Thanks, the changes look mostly good to me. The slot stats need to be > > > > > initialized in RestoreSlotFromDisk and ReplicationSlotCreate, not in > > > > > StartupDecodingContext. Apart from that, I have moved the declaration > > > > > of UpdateDecodingStats from slot.h back to logical.h. I have also > > > > > added/edited a few comments. Please check and let me know what do you > > > > > think of the attached? > > > > > > > > The patch moves slot stats to the ReplicationSlot data that is on the > > > > shared memory. If we have a space to store the statistics in the > > > > shared memory can we simply accumulate the stats there and make them > > > > persistent without using the stats collector? > > > > > > > > > > But for that, we need to write to file at every commit/abort/prepare > > > (decode of commit) which I think will incur significant overhead. > > > Also, we try to write after few commits then there is a danger of > > > losing them and still there could be a visible overhead for small > > > transactions. > > > > > > > I preferred not to persist this information to file, let's have stats > > collector handle the stats persisting. > > > > Sawada-San, I would like to go ahead with your > "Use-HTAB-for-replication-slot-statistics" unless you think otherwise? I agree that it's better to use the stats collector. So please go ahead. Regards, -- Masahiko Sawada EDB: https://www.enterprisedb.com/
Commits
-
Doc: Update logical decoding stats information.
- 0c6b92d9c6fb 14.0 landed
-
Fix tests for replication slots stats.
- fc69509131c3 14.0 landed
-
Update replication statistics after every stream/spill.
- 592f00f8dec6 14.0 landed
-
Fix the computation of slot stats for 'total_bytes'.
- 205f466282be 14.0 landed
-
Another try to fix the test case added by commit f5fc2f5b23.
- 51ef9173030c 14.0 landed
-
Use HTAB for replication slot statistics.
- 3fa17d37716f 14.0 landed
-
Fix test case added by commit f5fc2f5b23.
- c64dcc7fee5f 14.0 landed
-
Add information of total data processed to replication slot stats.
- f5fc2f5b23d1 14.0 landed
-
Use NameData datatype for slotname in stats.
- cca57c1d9bf7 14.0 landed