Re: Multi-Column List Partitioning - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject Re: Multi-Column List Partitioning
Date
Msg-id CAE9k0PkrDv+YMRD9DmZBRwG1r51pV-a6kFiUyLaRZ-EvX6QQ9Q@mail.gmail.com
Whole thread Raw
In response to Re: Multi-Column List Partitioning  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On Mon, Dec 20, 2021 at 7:04 PM Amit Langote <amitlangote09@gmail.com> wrote:
Hi,

On Mon, Dec 13, 2021 at 11:37 PM Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
>
> Hi,
>
> Is this okay?
>
> postgres=# CREATE TABLE t1 (a int, b int) PARTITION BY LIST ( a, a, a );
> CREATE TABLE
>
> postgres=# CREATE TABLE t1_1 PARTITION OF t1 FOR VALUES IN ((1, 2, 3), (4, 5, 6));
> CREATE TABLE
>
> postgres=# \d t1
>            Partitioned table "public.t1"
>  Column |  Type   | Collation | Nullable | Default
> --------+---------+-----------+----------+---------
>  a      | integer |           |          |
>  b      | integer |           |          |
> Partition key: LIST (a, a, a)
> Number of partitions: 1 (Use \d+ to list them.)

I'd say it's not okay for a user to expect this to work sensibly, and
I don't think it would be worthwhile to write code to point that out
to the user if that is what you were implying.

OK. As you wish.

--
With Regards,
Ashutosh Sharma.

pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Next
From: Andrew Bille
Date:
Subject: Re: [Proposal] Global temporary tables