Re: Multi-Column List Partitioning

Поиск
Список
Период
Сортировка
От Amit Langote
Тема Re: Multi-Column List Partitioning
Дата
Msg-id CA+HiwqGbJCxFsQ1mVB2fVrZPsW+QNF1hPcJPReCAYXQdr3zPmg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Multi-Column List Partitioning  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Ответы Re: Multi-Column List Partitioning  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Список pgsql-hackers
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.

-- 
Amit Langote
EDB: http://www.enterprisedb.com



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Gunnar \"Nick\" Bluth"
Дата:
Сообщение: [PATCH] pg_stat_toast v0.3
Следующее
От: Jakub Wartak
Дата:
Сообщение: RE: In-placre persistance change of a relation