Horton
Menu

Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vinod Sridharan <vsridh90@gmail.com>
Cc: niek.brasa@hitachienergy.com, pgsql-bugs@lists.postgresql.org
Date: 2025-04-12T03:00:31Z
Lists: pgsql-bugs 
Vinod Sridharan <vsridh90@gmail.com> writes:
>  -- create textops operator class without triconsistent

OK, got it, and I concur that we need to make shimTriConsistentFn()
restore the state of the entryRes array before it returns.  But
I don't understand why you're concerned about "However, this would
also reset it during the regular triConsistent check per tuple"?
I think the point is basically that this function is violating
the expectation that triconsistent functions not change the state
of that array.  That expectation doesn't depend on what the call
site is.

			regards, tom lane

Commits

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

  1. Fix GIN's shimTriConsistentFn to not corrupt its input.

  2. Fix some performance issues in GIN query startup.