Re: GSoC proposal - "make an unlogged table logged" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: GSoC proposal - "make an unlogged table logged"
Date
Msg-id 10144.1393867355@sss.pgh.pa.us
Whole thread Raw
In response to Re: GSoC proposal - "make an unlogged table logged"  (Stephen Frost <sfrost@snowman.net>)
Responses Re: GSoC proposal - "make an unlogged table logged"  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Robert Haas (robertmhaas@gmail.com) wrote:
>> On Mon, Mar 3, 2014 at 11:28 AM, Fabr�zio de Royes Mello
>> <fabriziomello@gmail.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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: patch: option --if-exists for pg_dump
Next
From: Tan Tran
Date:
Subject: Re: GSoC on WAL-logging hash indexes