Re: Proposal for unlogged tables

From: Andres Freund <andres(at)anarazel(dot)de>
To: Mark Zealey <mark(at)allaroundtheworld(dot)fr>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Proposal for unlogged tables
Date: 2016-01-04 17:16:40
Message-ID: 20160104171640.GF28025@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom McLoughlin 2016-01-06 08:08:02 Materialized view performance problems
Previous Message Mark Zealey 2016-01-04 17:12:22 Re: Proposal for unlogged tables