diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2021-02-23 12:15:09 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2021-02-23 12:15:09 -0300 |
| commit | d9d076222f5b94a85e0e318339cfc44b8f26022d (patch) | |
| tree | 246a3d9659c6d782033f30d454055eb3fd7d81f1 /src/backend/access/gist/gistxlog.c | |
| parent | 6f6f284c7ee44264eb3e128e2bf54d9276711d11 (diff) | |
| download | postgresql-d9d076222f5b94a85e0e318339cfc44b8f26022d.tar.gz | |
VACUUM: ignore indexing operations with CONCURRENTLY
As envisioned in commit c98763bf51bf, it is possible for VACUUM to
ignore certain transactions that are executing CREATE INDEX CONCURRENTLY
and REINDEX CONCURRENTLY for the purposes of computing Xmin; that's
because we know those transactions are not going to examine any other
tables, and are not going to execute anything else in the same
transaction. (Only operations on "safe" indexes can be ignored: those
on indexes that are neither partial nor expressional).
This is extremely useful in cases where CIC/RC can run for a very long
time, because that used to be a significant headache for concurrent
vacuuming of other tables.
Reviewed-by: Matthias van de Meent <boekewurm+postgres@gmail.com>
Reviewed-by: Masahiko Sawada <sawada.mshk@gmail.com>
Discussion: https://postgr.es/m/20210115133858.GA18931@alvherre.pgsql
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions