| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Rethinking opclass member checks and dependency strength |
| Date: | 2020-07-28 15:43:44 |
| Message-ID: | 1221226.1595951024@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com> writes:
> 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
Hmm ... I think you must have done something wrong. For me,
am-check-members-callback-5.patch still applies cleanly (just a few
small offsets), and it passes that test as well as the rest of
check-world. The cfbot agrees [1].
Maybe you didn't "make clean" before rebuilding?
regards, tom lane
[1] https://travis-ci.org/github/postgresql-cfbot/postgresql/builds/712599990
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-07-28 15:45:41 | Re: 13dev failed assert: comparetup_index_btree(): ItemPointer values should never be equal |
| Previous Message | James Coleman | 2020-07-28 15:40:14 | Re: 13dev failed assert: comparetup_index_btree(): ItemPointer values should never be equal |