| From: | Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Rethinking opclass member checks and dependency strength |
| Date: | 2020-07-28 14:51:15 |
| Message-ID: | 159594787542.781.16030655391691281794.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The following review has been posted through the commitfest application:
make installcheck-world: tested, failed
Implements feature: tested, failed
Spec compliant: not tested
Documentation: not tested
I've gone through the patch and applied on the master branch, other than a few hunks, and whether as suggested upthread, the default case for "switch (op->number)" should throw an error or not, I found that bloom regression is crashing.
-------------
test bloom ... FAILED (test process exited with exit code 2) 20 ms
+server closed the connection unexpectedly
+ This probably means the server terminated abnormally
+ before or while processing the request.
+connection to server was lost
-------------
The new status of this patch is: Waiting on Author
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-07-28 15:10:02 | 13dev failed assert: comparetup_index_btree(): ItemPointer values should never be equal |
| Previous Message | Tom Lane | 2020-07-28 14:35:54 | Re: printing oid with %d |