Re: pg_plan_advice

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_plan_advice
Date: 2026-03-19 22:43:48
Message-ID: 1504963.1773960228@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Do you think the idea of piggybacking the test_plan_advice run onto
> another run that we're already doing has any potential? That would
> reduce the incremental cost quite a lot, I think.

It would, but it's conceptually ugly and it might make it much harder
to detangle the cause of a failure, so I don't care for it much.

I don't have any great ideas here. Your point about the test having
helped to find a lot of bugs is compelling, and so is the fact that
it's seemingly exposing more issues we've not understood yet.
Maybe we can eventually buy back the cycles by not running it by
default, but clearly now is not the time for that.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-03-19 23:11:18 Re: pg_plan_advice
Previous Message Andres Freund 2026-03-19 22:21:59 Re: Don't synchronously wait for already-in-progress IO in read stream