| From: | Chaouki Dhib <chaodhib(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: the doc should mention one particular aspect of partial indexes |
| Date: | 2021-01-19 21:23:52 |
| Message-ID: | CAD6mX12NLTXTnwWz_qpOsKLsE8CZC3yXoU=ARjDeDpMDbhCzeA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
I guess it isn't. My apologies. This is something I ignored about PG
until now. Thank you for your reply.
Le lun. 18 janv. 2021 à 21:39, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
>
> PG Doc comments form <noreply(at)postgresql(dot)org> writes:
> > I think the documentation should mention one particular aspect of b-tree
> > partial indexes:
> > Say we have a row that satisfy a partial index's predicate. That row will be
> > referenced by the partial index. Say now that this row gets updated in such
> > a way that the updated row no longer satisfies the predicate. The entry of
> > that row in the index (more precisely, the row previous version) is still
> > kept in a leaf node of the b-tree until a VACUUM is issued on the index's
> > table.
>
> How is this different from the behavior for any other dead row version?
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jürgen Purtz | 2021-01-21 12:38:26 | Re: Additional Chapter for Tutorial - arch-dev.sgml |
| Previous Message | PG Doc comments form | 2021-01-19 10:16:58 | Windows Powershell |