Re: pgsql: snapshot scalability: cache snapshots using a xact completion co

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: snapshot scalability: cache snapshots using a xact completion co
Date: 2020-08-18 05:21:17
Message-ID: 1175198.1597728077@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> I'd written to Tom that I was planning to revert unless the number of
> failures were lower than initially indicated. But that actually seems to
> have come to pass (the failures are quicker to report because they don't
> run the subsequent tests, of course). I'd like to let the failures
> accumulate a bit longer, say until tomorrow Midday if I haven't figured
> it out by then. With the hope of finding some detail to help pinpoint
> the issue.

There's certainly no obvious pattern here, so I agree with waiting for
more data.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2020-08-18 10:26:31 pgsql: Avoid non-constant format string argument to fprintf().
Previous Message Andres Freund 2020-08-18 05:18:32 Re: pgsql: snapshot scalability: cache snapshots using a xact completion co

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2020-08-18 05:45:51 Print logical WAL message content
Previous Message Andres Freund 2020-08-18 05:18:32 Re: pgsql: snapshot scalability: cache snapshots using a xact completion co