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

From Fabrízio de Royes Mello
Subject Re: GSoC proposal - "make an unlogged table logged"
Date
Msg-id CAFcNs+qvrRLAYMuNXKfeUP+2z17-a+_zJ1j_RXjSxZBDE_gDzA@mail.gmail.com
Whole thread Raw
In response to Re: GSoC proposal - "make an unlogged table logged"  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: GSoC proposal - "make an unlogged table logged"  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
<div dir="ltr"><br />On Thu, Mar 6, 2014 at 4:42 PM, Robert Haas <<a
href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>wrote:<br />><br />><br />> I think this
isn'ta good design.  Per the discussion between Andres<br /> > and I, I think that I think you should do is make
ALTERTABLE .. SET<br />> LOGGED work just like VACUUM FULL, with the exception that it will set<br />> a
differentrelpersistence for the new relfilenode.  If you do it that<br /> > way, this will be less efficient, but
muchsimpler, and you might<br />> actually finish it in one summer.<br />><br /><br />Do it like 'VACUUM FULL'
forany wal_level?<br /><br />Regards,<br /><br />--<br />Fabrízio de Royes Mello<br /> Consultoria/Coaching
PostgreSQL<br/>>> Timbira: <a href="http://www.timbira.com.br">http://www.timbira.com.br</a><br />>> Blog
sobreTI: <a href="http://fabriziomello.blogspot.com">http://fabriziomello.blogspot.com</a><br /> >> Perfil
Linkedin:<a href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br />>>
Twitter:<a href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a></div> 

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: walsender doesn't send keepalives when writes are pending
Next
From: Robert Haas
Date:
Subject: Re: GSoC proposal - "make an unlogged table logged"