Re: [PATCH] Covering SPGiST index
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Borisov <pashkin.elfe@gmail.com>
Cc: David Steele <david@pgmasters.net>,
"Andrey M. Borodin" <x4mmm@yandex-team.ru>,
Anastasia Lubennikova <a.lubennikova@postgrespro.ru>,
Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-04-05T22:52:43Z
Lists: pgsql-hackers
Pavel Borisov <pashkin.elfe@gmail.com> writes: > In a v14 I forgot to add the test. PFA v15 I've committed this with a lot of mostly-cosmetic changes. The not-so-cosmetic bits had to do with confusion between the input data type and the leaf type, which isn't really your fault because it was there before :-(. One note is that I dropped the added regression test script (index_including_spgist.sql) entirely, because I couldn't see that it did anything that justified a permanent expenditure of test cycles. It looks like you made that by doing s/gist/spgist/g on index_including_gist.sql, which might be all right except that that script was designed to test GiST-specific implementation concerns that aren't too relevant to SP-GiST. AFAICT, removing that script had exactly zero effect on the test coverage shown by gcov. There are certainly bits of spgist that are depressingly under-covered, but I'm afraid we need custom-designed test cases to get at them. (wanders away wondering if the isolationtester could be used to test the concurrency-sensitive parts of spgvacuum.c ...) regards, tom lane
Commits
-
Support INCLUDE'd columns in SP-GiST.
- 09c1c6ab4bc5 14.0 landed
-
Rethink handling of pass-by-value leaf datums in SP-GiST.
- 1ebdec8c0329 14.0 landed