Re: performance of temporary vs. regular tables

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Joachim Worringen <joachim(dot)worringen(at)iathh(dot)de>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: performance of temporary vs. regular tables
Date: 2010-05-25 09:38:02
Message-ID: AANLkTilN0Qrf0NoHRhGW4VWuRyj1Gpfe5qpLzeNHNyBH@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

WAL does the same thing to DB journaling does to the FS.
Plus allows you to roll back (PITR).

As for the RAM, it will be in ram as long as OS decides to keep it in
RAM cache, and/or its in the shared buffers memory.
Unless you have a lot of doubt about the two, I don't think it makes
too much sens to setup ramdisk table space yourself. But try it, and
see yourself.
Make sure that you have logic in place, that would set it up, before
postgresql starts up, in case you'll reboot, or something.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Joachim Worringen 2010-05-25 09:52:20 Re: performance of temporary vs. regular tables
Previous Message Joachim Worringen 2010-05-25 09:32:14 Re: performance of temporary vs. regular tables