pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: terminate called after throwing an instance of 'std::bad_alloc'
Date: Tue, 20 Apr 2021 00:58:21 -0500
Message-ID: <20210420055821.GA17201@telsasoft.com> (raw)
In-Reply-To: <20210420053826.GM7256@telsasoft.com>
References: <20201003233045.GM8476@telsasoft.com>
	<20201004020127.zbrol2ypu6tg2bei@alap3.anarazel.de>
	<20201007230242.rnwsbnxywvthef3w@alap3.anarazel.de>
	<20201218235607.GC30237@telsasoft.com>
	<20210417021755.xdcqaqqt4y46wzt7@alap3.anarazel.de>
	<20210417024854.GL3315@telsasoft.com>
	<20210417031837.GM3315@telsasoft.com>
	<20210418001324.GP3315@telsasoft.com>
	<20210419164130.byegpfrw46mzagcu@alap3.anarazel.de>
	<20210420053826.GM7256@telsasoft.com>

On Tue, Apr 20, 2021 at 12:38:26AM -0500, Justin Pryzby wrote:
> I don't know if this is related to the other issues, but this seems leaky.

And it explains how the context use counter can exceed its threshold.

create or replace function fn() returns void language plpgsql as $$ declare rec int; begin SELECT relpages INTO rec FROM pg_class LIMIT 1; end $$;
explain analyze
SELECT fn()
FROM generate_series(1,99);

SELECT SUM(a) FROM (VALUES(1))a(a);

time PGOPTIONS='-cclient_min_messages=debug -clog_executor_stats=off -clog_min_duration_statement=-1 -cjit=on -cjit_above_cost=0 -cjit_inline_above_cost=0' psql ts -f jitleak.sql
...
psql:jitleak.sql:6: DEBUG:  recreating LLVM context after 100 uses

Question: does the jit context need to be recreated only when inlining is
enabled?  Or maybe it's better if it's not conditionalized like that..





view thread (28+ messages)  latest in thread

Message-ID: <20210420055821.GA17201@telsasoft.com>
Permalink:  ../20210420055821.GA17201@telsasoft.com/
Also on:    postgresql.org/message-id/20210420055821.GA17201@telsasoft.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, andres@anarazel.de, tgl@sss.pgh.pa.us
  Subject: Re: terminate called after throwing an instance of 'std::bad_alloc'
  In-Reply-To: <20210420055821.GA17201@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox