| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pluggable Indexes (was Re: rmgr hooks (v2)) |
| Date: | 2009-01-22 13:45:28 |
| Message-ID: | 1232631928.2327.862.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2009-01-22 at 14:52 +0200, Heikki Linnakangas wrote:
> Oleg Bartunov wrote:
> > as I understand, there are already plans to utilize this feature. If so,
> > we need to be more attentive by now.
>
> Is there? If I understood Simon correctly in the last paragraphs of
> these emails:
>
> http://archives.postgresql.org/message-id/1221470800.3913.1229.camel@ebony.2ndQuadrant
> http://archives.postgresql.org/message-id/1221555881.3913.1761.camel@ebony.2ndQuadrant
>
> he has no immediate use for this.
Immediate use cases for me would be
* ability to filter WAL records based on database or relation
* ability to recover quickly from various types of bug, for example if
new freespace code caused a corruption we would be able to sidestep it
and get the database up again quickly without doing resetxlog and losing
data.
Medium term
* bit map indexes
But this isn't just for me...
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-01-22 14:15:06 | Re: Pluggable Indexes (was Re: rmgr hooks (v2)) |
| Previous Message | Heikki Linnakangas | 2009-01-22 13:01:21 | Re: [Fwd: Re: Transactions and temp tables] |