Re: Common Table Expressions (WITH RECURSIVE) patch - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Common Table Expressions (WITH RECURSIVE) patch
Date
Msg-id 488E758F-111C-474F-9B03-473E9CED489C@hi-media.com
Whole thread Raw
In response to Re: Common Table Expressions (WITH RECURSIVE) patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Common Table Expressions (WITH RECURSIVE) patch  ("Hitoshi Harada" <umi.tanuki@gmail.com>)
List pgsql-hackers
-----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 usetuplestore_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-----


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: Block-level CRC checks
Next
From: pgsql@mohawksoft.com
Date:
Subject: Re: Block-level CRC checks