From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: REINDEX backend filtering |
Date: | 2021-03-15 16:30:43 |
Message-ID: | 0E0B73C0-EBC0-490A-9347-66A66E3338AE@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Mar 14, 2021, at 8:33 PM, Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>
> <v7-0001-Add-a-new-OUTDATED-filtering-facility-for-REINDEX.patch><v7-0002-Add-a-outdated-option-to-reindexdb.patch>
In the docs, 0001, "Fow now, the only dependency handled currently",
"Fow now" is misspelled, and "For now" seems redundant when used with "currently".
In the docs, 0002, "For now only dependency on collations are supported."
"dependency" is singular, "are" is conjugated for plural.
In the docs, 0002, you forgot to update doc/src/sgml/ref/reindexdb.sgml with the documentation for the --outdated switch.
In the tests, you check that REINDEX (OUTDATED) doesn't do anything crazy, but you are not really testing the functionality so far as I can see, as you don't have any tests which cause the collation to be outdated. Am I right about that? I wonder if you could modify DefineCollation. In addition to the providers "icu" and "libc" that it currently accepts, I wonder if it might accept "test" or similar, and then you could create a test in src/test/modules that compiles a "test" provider, creates a database with indexes dependent on something from that provider, stops the database, updates the test collation, ...?
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2021-03-15 16:34:29 | Re: archive status ".ready" files may be created too early |
Previous Message | Laurenz Albe | 2021-03-15 16:26:41 | Re: Confusing behavior of psql's \e |