Re: Why is parula failing?
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, tharar@amazon.com
Date: 2024-03-21T00:53:31Z
Lists: pgsql-hackers
Attachments
- debug_partition_prune_failures.patch (text/plain) patch
On Thu, 21 Mar 2024 at 12:36, Tom Lane <tgl@sss.pgh.pa.us> wrote: > So yeah, if we could have log_autovacuum_min_duration = 0 perhaps > that would yield a clue. FWIW, I agree with your earlier statement about it looking very much like auto-vacuum has run on that table, but equally, if something like the pg_index record was damaged we could get the same plan change. We could also do something like the attached just in case we're barking up the wrong tree. David
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Revert "Temporarily install debugging in partition_prune test"
- ec1a405adc24 17.0 landed
-
Temporarily install debugging in partition_prune test
- 1db689715d44 17.0 landed
-
Review wording on tablespaces w.r.t. partitioned tables
- a0390f6ca6c7 17.0 cited