Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Christoph Berg <cb(at)df7cb(dot)de>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED
Date: 2014-07-21 16:11:46
Message-ID: CAFcNs+oGfdLR4Fs2sAuqSbHadn7pLcPa_cFho4v1gcUprOqJqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 21, 2014 at 9:51 AM, Andres Freund <andres(at)2ndquadrant(dot)com>
wrote:
>
> On 2014-07-16 20:45:15 -0300, Fabrízio de Royes Mello wrote:
> > > The rewrite will read in the 'old' contents - but because it's done
> > > after the pg_class.relpersistence is changed they'll all not be marked
> > > as BM_PERMANENT in memory. Then the ALTER TABLE is rolled back,
> > > including the relpersistence setting. Which will unfortunately leave
> > > pages with the wrong persistency setting in memory, right?
> > >
> >
> > That means should I "FlushRelationBuffers(rel)" before change the
> > relpersistence?
>
> Did my explanation clarify the problem + possible solution sufficiently?
>

Yes, your explanation was enough. I didn't had time to working on it yet.
But I hope working on it today or tomorrow at least.

Regards,

--
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Braunstein, Alan 2014-07-21 18:14:00 Exporting Table-Specified BLOBs Only?
Previous Message Thomas Fanghaenel 2014-07-21 16:00:10 Re: Portability issues in TAP tests