the doc should mention one particular aspect of partial indexes

Started by PG Bug reporting formabout 5 years ago3 messagesdocs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/sql-vacuum.html
Description:

Hi,

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.

So in short, an update on the index's predicate column results in no direct
change on the index whereas a change on an index column is reflected as soon
as the change has been committed. I think the documentation should mention
this specificity in some way since it can have impact in terms of index
design. I couldn't find a mention of this behavior anywhere in the doc.

Kind regards,
Chaouki Dhib

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: PG Bug reporting form (#1)
Re: the doc should mention one particular aspect of partial indexes

PG Doc comments form <noreply@postgresql.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

#3Chaouki Dhib
chaodhib@gmail.com
In reply to: Tom Lane (#2)
Re: the doc should mention one particular aspect of partial indexes

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@sss.pgh.pa.us> a écrit :

Show quoted text

PG Doc comments form <noreply@postgresql.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