On Tue, 2 Jun 2020 at 15:15, Amit Kapila wrote:
>
> On Tue, Jun 2, 2020 at 11:30 AM Masahiko Sawada
> wrote:
> >
> > On Tue, 2 Jun 2020 at 14:50, Amit Kapila wrote:
> > >
> > > On Tue, Jun 2, 2020 at 10:22 AM Amit Kapila
> > > wrote:
> > > >
> > > > On Tue, Jun 2, 2020 at 9:10 AM Masahiko Sawa
On Tue, Jun 2, 2020 at 11:30 AM Masahiko Sawada
wrote:
>
> On Tue, 2 Jun 2020 at 14:50, Amit Kapila wrote:
> >
> > On Tue, Jun 2, 2020 at 10:22 AM Amit Kapila wrote:
> > >
> > > On Tue, Jun 2, 2020 at 9:10 AM Masahiko Sawada
> > > wrote:
> > > >
> > >
> > > > Please find attached patch.
> > > >
On Tue, 2 Jun 2020 at 14:50, Amit Kapila wrote:
>
> On Tue, Jun 2, 2020 at 10:22 AM Amit Kapila wrote:
> >
> > On Tue, Jun 2, 2020 at 9:10 AM Masahiko Sawada
> > wrote:
> > >
> >
> > > Please find attached patch.
> > >
> >
> > On a quick look, it seems fine but I will look in more detail and let
On Tue, Jun 2, 2020 at 10:22 AM Amit Kapila wrote:
>
> On Tue, Jun 2, 2020 at 9:10 AM Masahiko Sawada
> wrote:
> >
>
> > Please find attached patch.
> >
>
> On a quick look, it seems fine but I will look in more detail and let
> you know if I have any feedback.
>
I am not sure if we need to add
On Tue, Jun 2, 2020 at 9:10 AM Masahiko Sawada
wrote:
>
> Hi all,
>
> When reading pg_stat_replication doc of PG13, I thought it's better to
> mention that tracking of spilled transactions works only for logical
> replication like we already mentioned about replication lag tracking:
>
>
>La
