Horton
Menu

Re: Why is parula failing?

David Rowley <dgrowleyml@gmail.com>

View thread
From: David Rowley <dgrowleyml@gmail.com>
To: "Tharakan, Robins" <tharar@amazon.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2024-03-27T02:11:15Z
Lists: pgsql-hackers 
On Tue, 26 Mar 2024 at 21:03, Tharakan, Robins <tharar@amazon.com> wrote:
>
> > David Rowley <dgrowleyml@gmail.com> writes:
> > It would be good to have log_autovacuum_min_duration = 0 on this machine for a while.
>
> - Have set log_autovacuum_min_duration=0 on parula and a test run came out okay.
> - Also added REL_16_STABLE to the branches being tested (in case it matters here).

Thanks for doing that.

I see PG_16_STABLE has failed twice already with the same issue.  I
don't see any autovacuum / autoanalyze in the log, so I guess that
rules out auto vacuum activity causing this.

Unfortunately, REL_16_STABLE does not have the additional debugging,
so don't get to know what reltuples was set to.

David

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Revert "Temporarily install debugging in partition_prune test"

  2. Temporarily install debugging in partition_prune test

  3. Review wording on tablespaces w.r.t. partitioned tables