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 01:59:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

 Tom> Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
 >> Yup, fails the same way on an --enable-cassert build of 8.3.7.

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

This is the one I've been using:

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

set work_mem=64;

select t.a, t, t.a from foo(100000) t limit 1;
                              a                               |         t         |   a   
 \x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F\x7F | ("foo 1","bar 1") | foo 1
(1 row)


In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2009-03-30 02:01:03
Subject: Re: Re: [COMMITTERS] pgsql: Temporarily (I hope) disableflattening of IN/EXISTS sublinks
Previous:From: Tom LaneDate: 2009-03-30 01:55:36
Subject: Re: TupleTableSlot API problem

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