Re: GSoC proposal - "make an unlogged table logged"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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-03-03 17:22:35
Message-ID: 10144.1393867355@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
>> On Mon, Mar 3, 2014 at 11:28 AM, Fabrzio de Royes Mello
>> <fabriziomello(at)gmail(dot)com> wrote:
>>> Is the TODO item "make an unlogged table logged" [1] a good GSoC project?

>> I'm pretty sure we found some problems in that design that we couldn't
>> figure out how to solve. I don't have a pointer to the relevant
>> -hackers discussion off-hand, but I think there was one.

> ISTR the discussion going something along the lines of "we'd have to WAL
> log the entire table to do that, and if we have to do that, what's the
> point?".

IIRC, the reason you'd have to do that is to make the table contents
appear on slave servers. If you don't consider replication then it might
seem easier.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tan Tran 2014-03-03 17:39:32 Re: [HACKERS] GSoC on WAL-logging hash indexes
Previous Message Alvaro Herrera 2014-03-03 17:18:35 Re: patch: option --if-exists for pg_dump