Re: create table in memory

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Peter Kroon <plakroon(at)gmail(dot)com>
Cc: Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: create table in memory
Date: 2012-11-27 15:29:14
Message-ID: CAHyXU0yEvcsk-QsfvGvXmSbypdjWWMVtey--fEQQLrww9KHnOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Nov 23, 2012 at 4:09 AM, Peter Kroon <plakroon(at)gmail(dot)com> wrote:
> I've put up a small test case for creating TEMP and UNLOGGED tables.
> DROP TABLE IF EXISTS test CASCADE;
> CREATE TEMP TABLE test(
> id serial,
> the_value text
> );
> Exec time: 54ms
>
> DROP TABLE IF EXISTS test CASCADE;
> CREATE UNLOGGED TABLE test(
> id serial,
> the_value text
> );
> Exec time: 198ms
>
> There is a significant difference.
>
> Also I need those tables per session, so creating and dropping with TEMP
> tables appear to be faster.

Performance of creating tables is going to be storage bound. what are
your performance requirements? Even if the temp table itself is moved
to ramdisk you have catalog updating. Usually from performance
standpoint, creation of temp tables is not interesting -- but there
are exceptions. If you need extremely fast creation/drop of tempe
tables, you probably need to reorganize into permanent table with
session local records using various tricks.

merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Hari Babu 2012-11-27 15:33:35 Renamng the file "MSG00001.bin" to "MSG00001.msg" for internal usage placed in src/bin/pgevent
Previous Message Tom Lane 2012-11-27 15:06:14 Re: Restore postgres to specific time