From: Andres Freund <andres@anarazel.de>
To: Mark Zealey <mark@allaroundtheworld.fr>
Cc: pgsql-performance@postgresql.org
Subject: Re: Proposal for unlogged tables
Date: Mon, 4 Jan 2016 18:16:40 +0100
Message-ID: <20160104171640.GF28025@awork2.anarazel.de> (raw)
In-Reply-To: <568AA7F6.5050107@allaroundtheworld.fr>
References: <568A429C.2010507@allaroundtheworld.fr>
<568A8168.1070900@zioup.com>
<568A83F0.7050904@allaroundtheworld.fr>
<20160104161234.GE28025@awork2.anarazel.de>
<568AA7F6.5050107@allaroundtheworld.fr>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 2016-01-04 19:12:22 +0200, Mark Zealey wrote:
> If there was a command to flush a specific unlogged table to disk it would
> work around all these issues no? Perhaps if you marked the table as read
> only at the same time it would flush it to disk and ensure no more data
> could be written to it eg (ALTER TABLE ... SET READ ONLY on an unlogged
> table would flush + not truncate after crash). In our case this would be
> great as we want to use these as permanent tables for speed; but after an
> initial data dump we don't change the data again so we could just do this at
> the end of the import process.
It's more complex than that, even unmodified tables need to be processed
by vacuum every now and then (xid wraparound handling). It probably
possible to work around such things, but it's not a line or ten.
Andres
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: andres@anarazel.de, mark@allaroundtheworld.fr
Subject: Re: Proposal for unlogged tables
In-Reply-To: <20160104171640.GF28025@awork2.anarazel.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