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

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Thom Brown <thom(at)linux(dot)com>
Subject: Re: GSoC proposal - "make an unlogged table logged"
Date: 2014-03-06 20:05:25
Message-ID: CAFcNs+qkcWPySJARNFrBHDWAJjLMc0xfRJTodFq4rULtreDJrA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 6, 2014 at 5:04 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, Mar 6, 2014 at 2:52 PM, Fabrízio de Royes Mello
> <fabriziomello(at)gmail(dot)com> wrote:
> > On Thu, Mar 6, 2014 at 4:42 PM, Robert Haas <robertmhaas(at)gmail(dot)com>
wrote:
> >> I think this isn't a good design. Per the discussion between Andres
> >> and I, I think that I think you should do is make ALTER TABLE .. SET
> >> LOGGED work just like VACUUM FULL, with the exception that it will set
> >> a different relpersistence for the new relfilenode. If you do it that
> >> way, this will be less efficient, but much simpler, and you might
> >> actually finish it in one summer.
> >>
> >
> > Do it like 'VACUUM FULL' for any wal_level?
>
> Yep. Anything else appears to be a research problem.
>

I'll change the proposal. Thanks a lot!

Grettings,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-03-06 20:06:33 Re: Fwd: patch: make_timestamp function
Previous Message Robert Haas 2014-03-06 20:04:05 Re: GSoC proposal - "make an unlogged table logged"