Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists

From: Michał Albrycht <michalalbrycht(at)gmail(dot)com>
To: Michał Albrycht <michalalbrycht(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists
Date: 2021-01-27 17:10:47
Message-ID: CACsoHGBgt=v6e9bZNyA5Sbp-6oEEsCMNgm5XfeEhRW+2xG5gTg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Argh! I pasted the wrong value of volume_id in my examples. Number 1 should
be replaced with 2 so correct insert should look like this:

INSERT INTO dir (volume_id, path) VALUES
(2, 'abc'),
(2, 'def'),
(2, 'ghi');

And queries:
SELECT * FROM dir WHERE volume_id=2 AND path='abc';
SELECT * FROM dir WHERE volume_id=2 AND (path='abc' OR path='def');
SELECT * FROM dir_part_2 WHERE volume_id=2 AND (path='abc' or path='def');

Sorry for creating unnecessary confusion.

Michał Albrycht

śr., 27 sty 2021 o 18:03 PG Bug reporting form <noreply(at)postgresql(dot)org>
napisał(a):

> The following bug has been logged on the website:
>
> Bug reference: 16840
> Logged by: Michał Albrycht
> Email address: michalalbrycht(at)gmail(dot)com
> PostgreSQL version: 13.1
> Operating system: Ubuntu 18
> Description:
>
> Lets create a table partitioned by hash:
>
> CREATE TABLE dir (
> id SERIAL,
> volume_id BIGINT,
> path TEXT
> ) PARTITION BY HASH (volume_id);
>
>
> Now let's create just one partition:
>
> CREATE TABLE dir_part_2 PARTITION OF dir FOR VALUES WITH (modulus 3,
> remainder 2);
>
> Insert sample value:
>
> INSERT INTO dir (volume_id, path) VALUES
> (1, 'abc'),
> (1, 'def'),
> (1, 'ghi');
>
> Queries to verify db state:
> SELECT * FROM dir WHERE volume_id=1 AND path='abc'; -- returns 1 row - OK
> SELECT * FROM dir WHERE volume_id=1 AND (path='abc' OR path='def') --
> returns 0 rows - NOT OK!
> SELECT * FROM dir_part_2 WHERE volume_id=1 AND (path='abc' or path='def')
> --
> returns 2 rows - OK
>
> Now lets add missing partitions:
> CREATE TABLE dir_part_0 PARTITION OF dir FOR VALUES WITH (modulus 3,
> remainder 0);
> CREATE TABLE dir_part_1 PARTITION OF dir FOR VALUES WITH (modulus 3,
> remainder 1);
>
> And run problematic query one more time:
> SELECT * FROM dir WHERE volume_id=1 AND (path='abc' OR path='def') --
> returns 2 rows - OK
>
>
> So Postgres silently fails to find a rows, and does not throw any error
> when
> not all hash partitions are present.
>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michał Albrycht 2021-01-27 17:19:47 Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists
Previous Message PG Bug reporting form 2021-01-27 17:02:21 BUG #16840: Rows not found in table partitioned by hash when not all partitions exists