Re: read-only UNLOGGED tables

From: Leonardo Francalanci <m_lists(at)yahoo(dot)it>
To: Gianni Ciolli <gianni(dot)ciolli(at)2ndquadrant(dot)it>, pgsql-general(at)postgresql(dot)org
Subject: Re: read-only UNLOGGED tables
Date: 2011-03-31 11:24:01
Message-ID: 782924.22118.qm@web29020.mail.ird.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I suppose that a similar effect could be achieved by something like
>
> CREATE TABLE mytable_logged AS
> SELECT * FROM mytable_unlogged;
>
> which would not produce WAL:

yes, but it would mean re-writing the whole data + re-creating the indexes.

I didn't know that some statements don't write WAL at all if wal_level is
minimal (they just fsync at the end). Couldn't that be done in the
UNLOGGED to "regular" case? That is: if wal_level is minimal, you can
transform an unlogged table into a logged one, without having to rewrite
data + indexes: "just" fsync it and be done with it.

Wouldn't that be useful?

Leonardo

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Selena Deckelmann 2011-03-31 12:05:12 Re: foreign data wrappers
Previous Message Julia Jacobson 2011-03-31 10:32:28 Re: Linking against static libpq using Visual C++