Re: ExecForceStoreMinimalTuple leaks memory like there's no tomorrow

Hi, On 2019-04-18 19:04:09 -0700, Andres Freund wrote: > On 2019-04-15 22:46:56 -0400, Tom Lane wrote: > > Using HEAD, > > > > create table t1 as select generate_series(1,4000) id; > > vacuum analyze t1; > > explain select * from t1, t1 t1b where t1.id = t1b.id; > > -- should indicate a hash

Re: ExecForceStoreMinimalTuple leaks memory like there's no tomorrow

Hi, On 2019-04-15 22:46:56 -0400, Tom Lane wrote: > Using HEAD, > > create table t1 as select generate_series(1,4000) id; > vacuum analyze t1; > explain select * from t1, t1 t1b where t1.id = t1b.id; > -- should indicate a hash join > explain analyze select * from t1, t1 t1b where t1.id = t1b

Re: ExecForceStoreMinimalTuple leaks memory like there's no tomorrow

On Mon, Apr 15, 2019 at 10:46:56PM -0400, Tom Lane wrote: > create table t1 as select generate_series(1,4000) id; > vacuum analyze t1; > explain select * from t1, t1 t1b where t1.id = t1b.id; > -- should indicate a hash join > explain analyze select * from t1, t1 t1b where t1.id = t1b.id; > >

ExecForceStoreMinimalTuple leaks memory like there's no tomorrow

Using HEAD, create table t1 as select generate_series(1,4000) id; vacuum analyze t1; explain select * from t1, t1 t1b where t1.id = t1b.id; -- should indicate a hash join explain analyze select * from t1, t1 t1b where t1.id = t1b.id; ... watch the process's memory consumption bloat. (It runs