From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Jim Nasby <jim(at)nasby(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GSoC proposal - "make an unlogged table logged" |
Date: | 2014-04-03 11:41:55 |
Message-ID: | 20140403114155.GG2556@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2014-04-03 13:38:29 +0300, Heikki Linnakangas wrote:
> On 04/01/2014 08:58 PM, Andres Freund wrote:
> >On 2014-04-01 12:56:04 -0500, Jim Nasby wrote:
> >>On 3/4/14, 8:50 AM, Andres Freund wrote:
> >>>Can't that be solved by just creating the permanent relation in a new
> >>>relfilenode? That's equivalent to a rewrite, yes, but we need to do that
> >>>for anything but wal_level=minimal anyway.
> >>
> >>Maybe I'm missing something, but doesn't this actually involve writing the data twice? Once into WAL and again into the relation itself?
> >
> >Yes. But as I said, that's unavoidable for anything but
> >wal_level=minimal.
>
> Ideally, you would *only* write the data to WAL, when you do ALTER TABLE ...
> SET LOGGED. There's no fundamental reason you need to rewrite the
> heap, too.
As another point: What's the advantage of that? The amount of writes
will be the same, no? It doesn't seem to be all that interesting that
a second filenode exists temporarily?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-04-03 11:43:37 | Re: json(b) equality rules |
Previous Message | Andres Freund | 2014-04-03 11:37:53 | Re: GSoC proposal - "make an unlogged table logged" |