Re: TABLESAMPLE patch is really in pretty sad shape - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: TABLESAMPLE patch is really in pretty sad shape
Date
Msg-id 20150716133359.GN2301@postgresql.org
Whole thread Raw
In response to Re: TABLESAMPLE patch is really in pretty sad shape  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: TABLESAMPLE patch is really in pretty sad shape
Re: TABLESAMPLE patch is really in pretty sad shape
List pgsql-hackers
Petr Jelinek wrote:
> On 2015-07-13 00:36, Tom Lane wrote:

> >PS: now that I've written this rant, I wonder why we don't redesign the
> >index AM API along the same lines.  It probably doesn't matter much at
> >the moment, but if we ever get serious about supporting index AM
> >extensions, I think we ought to consider doing that.
> 
> +1
> 
> I think this is very relevant to the proposed sequence am patch as well.

Hmm, how would this work?  Would we have index AM implementation run
some function that register their support methods somehow at startup?
Hopefully we're not going to have the index AMs become shared libraries.

In any case, if indexes AMs and sequence AMs go this route, that
probably means the column store AM we're working on will probably have
to go the same route too.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: TABLESAMPLE patch is really in pretty sad shape
Next
From: Fujii Masao
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file