On Wed, Aug 27, 2025 at 9:36 PM Ashutosh Bapat
wrote:
>
> On Thu, Aug 28, 2025 at 5:56 AM Masahiko Sawada wrote:
> >
> > On Tue, Aug 26, 2025 at 2:45 AM Ashutosh Bapat
> > wrote:
> > >
> > > Hi Masahiko,
> > > Thanks for your inputs.
> > >
> > > On Tue, Aug 26, 2025 at 2:17 AM Masahiko Sawada
On Tue, Sep 23, 2025 at 6:04 PM Andres Freund wrote:
>
> Hi,
>
> On 2025-09-23 17:45:19 +0530, Ashutosh Bapat wrote:
> > On Tue, Sep 23, 2025 at 11:30 AM Masahiko Sawada
> > wrote:
> > >
> > > On Wed, Aug 27, 2025 at 9:36 PM Ashutosh Bapat
> > > wrote:
> > > >
> > > > Ok. I am interested in kno
Hi,
On 2025-09-23 17:45:19 +0530, Ashutosh Bapat wrote:
> On Tue, Sep 23, 2025 at 11:30 AM Masahiko Sawada
> wrote:
> >
> > On Wed, Aug 27, 2025 at 9:36 PM Ashutosh Bapat
> > wrote:
> > >
> > > Ok. I am interested in knowing how you think we should keep track of
> > > the high watermark.
> > >
On Tue, Sep 23, 2025 at 11:30 AM Masahiko Sawada wrote:
>
> On Wed, Aug 27, 2025 at 9:36 PM Ashutosh Bapat
> wrote:
> >
> > Ok. I am interested in knowing how you think we should keep track of
> > the high watermark.
> >
> > Do we keep it updated as new maxima are found? And keep reporting the
>
On Thu, Aug 28, 2025 at 5:56 AM Masahiko Sawada wrote:
>
> On Tue, Aug 26, 2025 at 2:45 AM Ashutosh Bapat
> wrote:
> >
> > Hi Masahiko,
> > Thanks for your inputs.
> >
> > On Tue, Aug 26, 2025 at 2:17 AM Masahiko Sawada
> > wrote:
> >
> > > On Wed, Aug 13, 2025 at 5:40 AM Ashutosh Bapat
> > >
On Tue, Aug 26, 2025 at 2:45 AM Ashutosh Bapat
wrote:
>
> Hi Masahiko,
> Thanks for your inputs.
>
> On Tue, Aug 26, 2025 at 2:17 AM Masahiko Sawada wrote:
>
> > On Wed, Aug 13, 2025 at 5:40 AM Ashutosh Bapat
> > wrote:
> >
> > Thank you for starting the thread about this topic. This is one of t
Hi,
On Tue, Aug 26, 2025 at 09:48:04AM +, Bertrand Drouvot wrote:
> Hi,
>
> On Tue, Aug 26, 2025 at 02:56:14PM +0530, Ashutosh Bapat wrote:
> > On Mon, Aug 25, 2025 at 6:28 PM Bertrand Drouvot
> > wrote:
> > > > I didn't know this is how it works. Thanks for correcting me. In that
> > > > ca
>
> >
> > > If we are going
> > > to report so much statistics about the contents of the reorder buffer,
> > > is it better to have a separate view pg_stat_reorder_buffer for the
> > > same?
> >
> > Given logical decoding can be used also by regular backend processes,
> > I guess that such dynamic
Hi,
On Tue, Aug 26, 2025 at 02:56:14PM +0530, Ashutosh Bapat wrote:
> On Mon, Aug 25, 2025 at 6:28 PM Bertrand Drouvot
> wrote:
> > > I didn't know this is how it works. Thanks for correcting me. In that
> > > case, I think we should
> > > add a column in pg_stat_replication_slots reporting the n
Hi Masahiko,
Thanks for your inputs.
On Tue, Aug 26, 2025 at 2:17 AM Masahiko Sawada wrote:
> On Wed, Aug 13, 2025 at 5:40 AM Ashutosh Bapat
> wrote:
>
> Thank you for starting the thread about this topic. This is one of the
> topics that I've been eager to address. Here are some random comment
On Mon, Aug 25, 2025 at 6:28 PM Bertrand Drouvot
wrote:
> > I didn't know this is how it works. Thanks for correcting me. In that
> > case, I think we should
> > add a column in pg_stat_replication_slots reporting the number of
> > times the memory limit is reached since the last reset. I am +0.5
Hi,
On Wed, Aug 13, 2025 at 5:40 AM Ashutosh Bapat
wrote:
>
> Hi All,
> The question of how to tune logical_decoding_work_mem has come up a
> few times in the context of customer cases. If it is too low then the
> changes are spilled to disk, slowing down replication and consuming
> disk space. I
Hi,
On Mon, Aug 25, 2025 at 01:48:42PM +0530, Ashutosh Bapat wrote:
> On Fri, Aug 22, 2025 at 11:43 AM Bertrand Drouvot
> wrote:
> >
> > Yes as long as subtrans are not involved. But if say I've one transaction
> > made of
> > 1500 subtrans, I'd get something like:
> >
> > slot_name | spill_
On Fri, Aug 22, 2025 at 11:43 AM Bertrand Drouvot
wrote:
>
> Hi Ashutosh,
>
> On Thu, Aug 21, 2025 at 07:26:41PM +0530, Ashutosh Bapat wrote:
> > Hi Bertrand,
> > Thanks for your response. I am glad that you have found the proposal
> > to be generally useful.
> >
> > On Thu, Aug 14, 2025 at 3:50 P
Hi Ashutosh,
On Thu, Aug 21, 2025 at 07:26:41PM +0530, Ashutosh Bapat wrote:
> Hi Bertrand,
> Thanks for your response. I am glad that you have found the proposal
> to be generally useful.
>
> On Thu, Aug 14, 2025 at 3:50 PM Bertrand Drouvot
> wrote:
> >
> > > Using these trendlines, a user may
Hi Bertrand,
Thanks for your response. I am glad that you have found the proposal
to be generally useful.
On Thu, Aug 14, 2025 at 3:50 PM Bertrand Drouvot
wrote:
>
> > Using these trendlines, a user may decide to keep
> > logical_decoding_work_mem to minimum and thus let all the large
> > transac
Hi,
On Wed, Aug 13, 2025 at 06:09:47PM +0530, Ashutosh Bapat wrote:
> Hi All,
> The question of how to tune logical_decoding_work_mem has come up a
> few times in the context of customer cases.
Same here.
> If it is too low then the
> changes are spilled to disk, slowing down replication and con
17 matches
Mail list logo
