Re: Replication slot stats misgivings - Mailing list pgsql-hackers

From vignesh C
Subject Re: Replication slot stats misgivings
Date
Msg-id CALDaNm2g27Y_UJdXq2EAdSLqfnktD6Ero3CKbaDUgw-tr35NcA@mail.gmail.com
Whole thread Raw
In response to Re: Replication slot stats misgivings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Replication slot stats misgivings  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Sun, Apr 18, 2021 at 3:51 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I wrote:
> > The buildfarm suggests that this isn't entirely stable:
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2021-04-17%2011%3A14%3A49
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bichir&dt=2021-04-17%2016%3A30%3A15
>
> Oh, I missed that hyrax is showing the identical symptom:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hyrax&dt=2021-04-16%2007%3A05%3A44
>
> So you might try CLOBBER_CACHE_ALWAYS to see if you can reproduce it
> that way.
>

I will try to check and identify why it is failing.

Regards,
Vignesh



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: terminate called after throwing an instance of 'std::bad_alloc'
Next
From: Amit Kapila
Date:
Subject: Re: Replication slot stats misgivings