| From: | Jian He <hejian(dot)mark(at)gmail(dot)com> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | list all the Boolean flags in pg_class that are maintained lazily. |
| Date: | 2022-03-08 15:33:47 |
| Message-ID: | CAMV54g3sEbVfbQN7b0nT7Fgs-ummWhVVomX-y+NN8jw2=9YV9w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
PostgreSQL: Documentation: 14: 52.11. pg_class
<https://www.postgresql.org/docs/current/catalog-pg-class.html>
> Several of the Boolean flags in pg_class are maintained lazily: they are
> guaranteed to be true if that's the correct state, but may not be reset to
> false immediately when the condition is no longer true. For example,
> relhasindex is set by CREATE INDEX
> <https://www.postgresql.org/docs/current/sql-createindex.html>, but it is
> never cleared by DROP INDEX
> <https://www.postgresql.org/docs/current/sql-dropindex.html>. Instead,
> VACUUM <https://www.postgresql.org/docs/current/sql-vacuum.html> clears
> relhasindex if it finds the table has no indexes. This arrangement avoids
> race conditions and improves concurrency.
9 boolean flags, 1 already mentioned maintained lazily.
Is possible to list all the flags that maintained lazily. or just mention This
is only an estimate like *relpage *flags in the same page.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-03-08 16:38:39 | Re: Missing information about CREATE TRIGGER on temporary tables |
| Previous Message | PG Doc comments form | 2022-03-08 15:32:23 | Missing information about CREATE TRIGGER on temporary tables |