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

From Tom Lane
Subject Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
Date
Msg-id 1098251.1744426831@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.  (Vinod Sridharan <vsridh90@gmail.com>)
Responses Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
List 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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
Next
From: Vinod Sridharan
Date:
Subject: Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.