Skip site navigation (1) Skip section navigation (2)

Re: Pluggable Indexes

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pluggable Indexes
Date: 2009-01-24 13:51:35
Message-ID: 1232805095.2327.1415.camel@ebony.2ndQuadrant (view raw or whole thread)
Lists: pgsql-hackers
On Sat, 2009-01-24 at 09:57 +0000, Simon Riggs wrote:

> I agree we need an external module and I learned that lesson from the
> earier API proposal you mentioned. The supplied WAL filter plugin was/is
> a valid use for this and, as discussed, is the only practical way of
> doing WAL filtering. As I said, am happy to make a few mods to make that
> more acceptable.

I can change the contrib plugin to show how to exclude DROP DATABASE and
DROP TABLESPACE records, which is a common recovery scenario.

I'll produce the table filter plugin and release it to pgfoundry. We
currently have everything we need to make that work, AFAICS.

 Simon Riggs 
 PostgreSQL Training, Services and Support

In response to


pgsql-hackers by date

Next:From: Bernd HelmleDate: 2009-01-24 14:29:06
Subject: Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle
Previous:From: Euler Taveira de OliveiraDate: 2009-01-24 13:44:55
Subject: Re: duplicated tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group