Re: terminate called after throwing an instance of 'std::bad_alloc' - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: terminate called after throwing an instance of 'std::bad_alloc'
Date
Msg-id 20210420053826.GM7256@telsasoft.com
Whole thread Raw
In response to Re: terminate called after throwing an instance of 'std::bad_alloc'  (Andres Freund <andres@anarazel.de>)
Responses Re: terminate called after throwing an instance of 'std::bad_alloc'
List pgsql-hackers
I don't know if this is related to the other issues, but this seems leaky.

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

PGOPTIONS='-cclient_min_messages=debug -clog_executor_stats=on -clog_min_duration_statement=-1 -cjit=on
-cjit_above_cost=0-cjit_inline_above_cost=0' psql ts -f jitleak.sql
 
!       70172 kB max resident size

PGOPTIONS='-cclient_min_messages=debug -clog_executor_stats=on -clog_min_duration_statement=-1 -cjit=on
-cjit_above_cost=0-cjit_inline_above_cost=-1' psql ts -f jitleak.sql
 
!       25672 kB max resident size



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: select 'x' ~ repeat('x*y*z*', 1000);
Next
From: Peter Smith
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions