Re: alternative back-end block formats

From: Christian Convey <christian(dot)convey(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: alternative back-end block formats
Date: 2014-01-28 12:46:10
Message-ID: CAPfS4Zxn1hWvHcgz90sutxunrqCXuo-zUJUirQxrDNCN6UxcjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 28, 2014 at 5:42 AM, Cédric Villemain <cedric(at)2ndquadrant(dot)com>wrote:
...

> As written in the meeting notes, Tom Lane revealed an interest in
> pluggable storage. So it might be interesting to check that.
>
> https://wiki.postgresql.org/wiki/PgCon_2013_Developer_Meeting
>

Thanks. I just read those meeting notes, and also Josh Berkus' blog on the
topic:
http://www.databasesoup.com/2013/05/postgresql-new-development-priorities-2.html

I was only thinking to enable pluggable operations on a single, specified
heap page, probably as a function of which table owned the page. Josh's
blog seems to describe something a little broader in scope, although I
can't tell from that post exactly what functionality that entails.

Either way, this sounds like something I'd enjoy pitching in on, to
whatever extent I could be useful. Has anyone started work on this yet?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2014-01-28 13:01:14 Re: [Review] inherit support for foreign tables
Previous Message Christian Kruse 2014-01-28 11:58:23 Re: [PATCH] Use MAP_HUGETLB where supported (v3)