Hello,
in the meantime we managed to not trigger the OOM kill anymore and now
also don't have this problem with the negative costs anymore. We still
have one staging environment where this error is present, but we would
like to reclaim it. Is there some guidelines I can follow to debug
this?
Jan
On 7 December 2017 at 10:54, Jan Schulz <jasc@gmx.net> wrote:
> On 5 December 2017 at 22:30, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Don't suppose you'd like to step through btcostestimate() with
>> a debugger and see where it's going off the rails?
> I've never done debugging of a C program. If you give me some hints how to
> do that, I might be able to (Ubuntu, PG from the apt repository).
> Is there any debug log I might need to enable to get some similar information?
