[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Common Table Expressions (WITH RECURSIVE) patch
From:       Dimitri Fontaine <dfontaine () hi-media ! com>
Date:       2008-09-30 19:39:10
Message-ID: 488E758F-111C-474F-9B03-473E9CED489C () hi-media ! com
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Le 30 sept. 08 à 20:03, Tom Lane a écrit :
> 	set_read_position(tupstore, &local_read_position);
> 	tuple = tuplestore_gettuple(tupstore, ...);
> 	get_read_position(tupstore, &local_read_position);
>
> rather than just tuplestore_gettuple.  The set/get functions will be
> cheap enough that this is no big deal.  (Or maybe we should just
> provide a wrapper function that does this sequence?)

It seems to me to share some ideas with the MemoryContext concept:  
what about a TupstoreContext associated with tuplestore, you get a  
common default one if you don't register your own, and use
	tuplestore_gettuple(MyTupstoreContext, ...);

Maybe some other API would benefit from the idea?

Regards,
- --
dim


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkjigF4ACgkQlBXRlnbh1bkycQCgqs/+JBOd0SiN4xvKwLgEgi9F
BOYAoLm0Se6zs8cEAnoTlH6de7pLLh/l
=kzm1
-----END PGP SIGNATURE-----

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[prev in list] [next in list] [prev in thread] [next in thread]