From: Joachim Worringen <joachim.worringen@iathh.de>
To: pgsql-performance@postgresql.org
Subject: Re: performance of temporary vs. regular tables
Date: Tue, 25 May 2010 11:52:20 +0200
Message-ID: <4BFB9DD4.5030702@iathh.de> (raw)
In-Reply-To: <AANLkTilN0Qrf0NoHRhGW4VWuRyj1Gpfe5qpLzeNHNyBH@mail.gmail.com>
References: <4BFB837C.6010005@iathh.de>
<AANLkTik4_exB6U3GlfLMNIgPSk0G3RVQ8fWBTzwekrke@mail.gmail.com>
<4BFB91A8.20805@iathh.de>
<AANLkTilBD97tBH3f3-RHvXcYy7t3yCt6-JxAtZ15mVkF@mail.gmail.com>
<4BFB991E.40407@iathh.de>
<AANLkTilN0Qrf0NoHRhGW4VWuRyj1Gpfe5qpLzeNHNyBH@mail.gmail.com>
Am 25.05.2010 11:38, schrieb Grzegorz Jaśkiewicz:
> 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.
Or until I commit the transaction? I have not completely disabled
sync-to-disk in my setup, as there are of course situations where new
data comes into the database that needs to be stored in a safe manner.
> 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.
That's what I thought about when mentioning "increased setup
complexity". Simply adding a keyword like "NONPERSISTENT" to the table
creation statement would be preferred...
Joachim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: joachim.worringen@iathh.de
Subject: Re: performance of temporary vs. regular tables
In-Reply-To: <4BFB9DD4.5030702@iathh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox