| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Pluggable Storage - Andres's take |
| Date: | 2018-10-16 06:51:07 |
| Message-ID: | CAA4eK1LojQBQ-0ha=cFxHgT=RoXYBAnWZuWPNfOLQ6468OZYpQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 16, 2018 at 12:37 AM Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
>
> I've examined code in pluggable-zheap branch and EDB github [1] and I
> didn't found anything related to "delete-marking" indexes as stated on
> slide #25 of presentation [2]. So, basically contract between heap
> and indexes is remain unchanged: once you update one indexed field,
> you have to update all the others.
>
Yes, this will be the behavior for the first version.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-10-16 07:18:26 | Re: pg11rc1 DROP INDEX: NOTICE: drop_trigger |
| Previous Message | Andres Freund | 2018-10-16 06:33:17 | Re: Large writable variables |