| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Failed assertion clauses != NIL |
| Date: | 2019-11-19 13:38:39 |
| Message-ID: | 20191119133839.5qj5zia4pkd3zldt@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Tue, Nov 19, 2019 at 01:50:51PM +0100, Manuel Rigger wrote:
>
> when building PostgreSQL with -enable-cassert, executing the following
> statements result in an assertion error:
>
> CREATE TABLE t0(c0 boolean, c1 boolean, c2 boolean);
> INSERT INTO t0 VALUES(FALSE, FALSE, FALSE);
> CREATE STATISTICS s0 ON c0, c2 FROM t0;
> ANALYZE;
> SELECT * FROM t0 WHERE t0.c2 OR t0.c1 OR t0.c0;
Yes, I can reproduce it too. mcv_get_match_bitmap expects that
stat_clauses will not be empty, but looks like in this situation
stat_clauses is indeed NIL. clauselist_selectivity_simple right before
actually doesn't insist on stat_clauses being non empty, probably it's
just too strict assert.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2019-11-19 13:45:54 | Re: Failed assertion clauses != NIL |
| Previous Message | Manuel Rigger | 2019-11-19 12:50:51 | Failed assertion clauses != NIL |