Re: [HACKERS] Big IN() clauses etc : feature proposal - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: [HACKERS] Big IN() clauses etc : feature proposal
Date
Msg-id 20060510192401.GQ99570@pervasive.com
Whole thread Raw
In response to Re: [HACKERS] Big IN() clauses etc : feature proposal  (PFC <lists@peufeu.com>)
Responses Re: [HACKERS] Big IN() clauses etc : feature proposal
Re: [HACKERS] Big IN() clauses etc : feature proposal
List pgsql-performance
On Tue, May 09, 2006 at 06:29:31PM +0200, PFC wrote:
>     You mean the cursors'storage is in fact the same internal machinery
>     as a  temporary table ?

Use the source, Luke...

See tuplestore_begin_heap in backend/utils/sort/tuplestore.c and
heap_create_with_catalog in backend/catalog/heap.c. You'll find that
creating a tuplestore is far easier than creating a temp table.

Perhaps it would be worth creating a class of temporary tables that used
a tuplestore, although that would greatly limit what could be done with
that temp table.

Something else worth considering is not using the normal catalog methods
for storing information about temp tables, but hacking that together
would probably be a rather large task.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: [HACKERS] Big IN() clauses etc : feature proposal
Next
From: PFC
Date:
Subject: Re: [HACKERS] Big IN() clauses etc : feature proposal