Skip site navigation (1) Skip section navigation (2)

Re: TupleTableSlot API problem

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TupleTableSlot API problem
Date: 2009-03-30 03:15:03
Message-ID: 874oxbaeh4.fsf@news-spur.riddles.org.uk (view raw or flat)
Thread:
Lists: pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

 >>> Yup, fails the same way on an --enable-cassert build of 8.3.7.

And on 8.2.13.

 Tom> Do you have a quick test case?  I just finished coding up my
 Tom> plan-C fix, and I need some test cases ...

 Andrew> This is the one I've been using:

This one is simpler and works on 8.2 as well:

create or replace function foo(n integer, out a text, out b text)
 returns setof record language sql
 as $f$ select 'foo '||i, 'bar '||i from generate_series(1,$1) i; $f$;

set work_mem=64;

select t.a, t, t.a from foo(100000) t limit 1;
ERROR:  invalid memory alloc request size 2139062147

-- 
Andrew.

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-03-30 03:29:56
Subject: Re: TupleTableSlot API problem
Previous:From: Fujii MasaoDate: 2009-03-30 02:32:36
Subject: Re: New trigger option of pg_standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group