| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: RAM-only temporary tables |
| Date: | 2008-11-11 19:13:01 |
| Message-ID: | 10595.1226430781@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Tom Lane wrote:
>> Heikki, would it be reasonable to fix things so that a nonexistent FSM
>> fork is semantically the same as an empty one, and not create FSM until
>> there's actually something to put in it?
> Possibly, but I'd like to understand what exactly the problem is. I
> tried running this:
> CREATE TEMPORARY TABLE footemp (id int4);
> DROP TABLE footemp;
> with pgbench -f, but can't see any meaningful difference between 8.3 and
> CVS HEAD. Both can do about 300 tpm, or 700-800 with fsync=off.
Try several thousand temp tables within one transaction.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Mayer | 2008-11-11 19:13:09 | Re: Re: Updated interval patches (SQL std output, ISO8601 intervals, and interval rounding) |
| Previous Message | Brendan Jurd | 2008-11-11 18:54:50 | Re: Re: Updated interval patches (SQL std output, ISO8601 intervals, and interval rounding) |