Re: pg_plan_advice - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_plan_advice
Date
Msg-id 1504963.1773960228@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_plan_advice  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pg_plan_advice
List pgsql-hackers
Robert Haas <robertmhaas@gmail.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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Don't synchronously wait for already-in-progress IO in read stream
Next
From: Robert Haas
Date:
Subject: Re: pg_plan_advice