BUG #18344: Pruning tables partitioned by bool range fails with invalid strategy

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: exclusion(at)gmail(dot)com
Subject: BUG #18344: Pruning tables partitioned by bool range fails with invalid strategy
Date: 2024-02-15 09:00:01
Message-ID: 18344-8d3f00bada6d09c6@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18344
Logged by: Alexander Lakhin
Email address: exclusion(at)gmail(dot)com
PostgreSQL version: 16.2
Operating system: Ubuntu 22.04
Description:

The following query:
CREATE TABLE t (b bool, i int) PARTITION BY RANGE (b, i);
CREATE TABLE tp PARTITION OF t FOR VALUES FROM (false, 0) TO (false, 1);
SELECT * FROM t WHERE b IS NOT true;

fails with ERROR: invalid strategy number 0.

Reproduced on REL_12_STABLE .. master.
The first bad commit for this anomaly is e0693faf7.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-02-15 11:58:18 BUG #18345: Specifying index parameters for a PRIMARY KEY column constraint is a syntax error
Previous Message PG Bug reporting form 2024-02-14 22:11:14 BUG #18343: Incorrect description in postgresql.conf for max_parallel_workers_per_gather