| From: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fractal tree indexing |
| Date: | 2013-02-13 13:24:51 |
| Message-ID: | 10468B76-66F7-4833-9E24-6CC686D656CD@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sent from my iPad
On 13-Feb-2013, at 18:21, Greg Stark <stark(at)mit(dot)edu> wrote
>
>
> Heikki was talking about a generic WAL record type that would just
> store a binary delta between the version of the block when it was
> locked and when it was unlocked. That would handle any extension
> cleanly as far as data modification goes as long as the extension was
> working through our buffer manager. It seems like an attractive idea
> to me.
>
>
How do we handle the case you mentioned, maybe a module that has been removed since a record was made? Is the solution that we encapsulate WAL from those kind of changes, and keep the WAL records same for everyone,irrespective whether they use an external module or not(I inferred this from Heikki's idea,or am I missing something here?)
Atri
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-02-13 13:28:36 | Re: Statistics and selectivity estimation for ranges |
| Previous Message | Amit Kapila | 2013-02-13 12:59:15 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |