Re: Memory deallocation after calling cast function

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Soroosh Sardari <soroosh(dot)sardari(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory deallocation after calling cast function
Date: 2014-06-17 15:32:37
Message-ID: 20140617153237.GD3666@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 3, 2014 at 03:59:45PM -0400, Tom Lane wrote:
> Soroosh Sardari <soroosh(dot)sardari(at)gmail(dot)com> writes:
> > I have problem with memory deallocation. look at the following queries
>
> > 1- create table test01(a) as select generate_series(1,100000000)::int8 ;
>
> Do it as, eg,
>
> create table test01(a) as select g::int8 from generate_series(1,100000000) g;
>
> SRFs in the SELECT targetlist tend to leak memory; this is not easily
> fixable, and nobody is likely to try hard considering the feature's on
> the edge of deprecation anyhow.

Uh, what is replacing SRFs? CTEs?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus de Oliveira 2014-06-17 15:34:36 How about a proper TEMPORARY TABLESPACE?
Previous Message Bruce Momjian 2014-06-17 15:29:21 Re: 9.4 release notes