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

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GSoC proposal - "make an unlogged table logged"
Date: 2014-03-04 04:36:30
Message-ID: CAFcNs+qb+Y-RqU1=iZ22+S0fOCGOXSbgy1Q2W8dt-SWoh4PsbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 3, 2014 at 5:47 PM, Andres Freund <andres(at)2ndquadrant(dot)com>
wrote:
>
> On 2014-03-03 12:44:26 -0800, Peter Geoghegan wrote:
> > On Mon, Mar 3, 2014 at 8:28 AM, Fabrízio de Royes Mello
> > <fabriziomello(at)gmail(dot)com> wrote:
> > > Is the TODO item "make an unlogged table logged" [1] a good GSoC
project?
> >
> > Another interesting project around unlogged tables would be to make it
> > possible to have unlogged indexes on fully-logged tables. That is
> > something that there was some discussion of before, that might be
> > easier.
>
> I'd actually say it's harder because it requires modifying the catalog
> or transparently introducing hacks similar to what unlogged matviews are
> doing, to make sure the index is marked invalid after a crash restart.
>

Unlogged matviews was disallowed [1].

[1]
http://www.postgresql.org/message-id/E1UZNrD-0008Eh-83@gemulon.postgresql.org

--
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 Fabrízio de Royes Mello 2014-03-04 04:38:04 Re: GSoC proposal - "make an unlogged table logged"
Previous Message Kouhei Kaigai 2014-03-04 04:27:27 Re: Custom Scan APIs (Re: Custom Plan node)