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

From Hannu Krosing
Subject Re: GSoC proposal - "make an unlogged table logged"
Date
Msg-id 5314BE80.3000209@2ndQuadrant.com
Whole thread Raw
In response to Re: GSoC proposal - "make an unlogged table logged"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: GSoC proposal - "make an unlogged table logged"  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
List pgsql-hackers
On 03/03/2014 05:22 PM, Tom Lane wrote:
> Stephen Frost <sfrost@snowman.net> writes:
...
>> 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.
So switch on logging and then perform CLUSTER/VACUUM FULL ?

Should this work, or is something extra needed ?

Cheers

-- 
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ




pgsql-hackers by date:

Previous
From: Tan Tran
Date:
Subject: Re: GSoC on WAL-logging hash indexes
Next
From: Andres Freund
Date:
Subject: Re: GSoC proposal - "make an unlogged table logged"