pg_hint_plan extension might be able to force a plan.
Also, I don’t know if perf probes & perf record/script could be useful for
creating a log of all the calls to do memory allocation along with the unwound
call stacks? Then analyzing that file? At least this can be done for a single
process,
On 4/19/2019 17:01, Justin Pryzby wrote:
Were you able to reproduce the issue in some minimized way ? Like after
joining fewer tables or changing to join with fewer join conditions ?
On Thu, Apr 18, 2019 at 05:21:28PM +0200, Tomas Vondra wrote:
It would be possible to do at least one of these
On Wed, Apr 17, 2019 at 11:52:44PM -0400, Gunther wrote:
> Hi guys. I don't want to be pushy, but I found it strange that after so much
Were you able to reproduce the issue in some minimized way ? Like after
joining fewer tables or changing to join with fewer join conditions ?
On Thu, Apr 18, 20
On Thu, Apr 18, 2019 at 6:01 AM Gunther wrote:
> Hi guys. I don't want to be pushy, but I found it strange that after so
> much lively back and forth getting to the bottom of this, suddenly my last
> nights follow-up remained completely without reply. I wonder if it even got
> received. For those
Thomas Kellerer writes:
> laurent.decha...@orange.com schrieb am 17.04.2019 um 16:33:
>> On jdbc it seems this is equivalent to write :
>> statement. setMaxRows(0); // parallelism authorized, which is the default.
>>
>> Thus on my jdbc basic program if I add :
>> statement. setMaxRows(100); //
