Re: Clarify restriction on partitioned tables primary key / unique indexes

From: Erik Rijkers <er(at)xs4all(dot)nl>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Clarify restriction on partitioned tables primary key / unique indexes
Date: 2022-09-02 10:01:09
Message-ID: 6b60dfd4-81c6-9361-3d47-d39513b1465a@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Op 02-09-2022 om 11:44 schreef David Rowley:
> Over on [1], there was a question about why it wasn't possible to
> create the following table:
>
> CREATE TABLE foobar(
> id BIGINT NOT NULL PRIMARY KEY,
> baz VARCHAR NULL DEFAULT NULL
> ) PARTITION BY HASH(my_func(id));
>
>
> The attached attempts to clarify these restrictions more accurately
> based on the current code's restrictions.
>
> If there's no objections or suggestions for better wording, I'd like
> to commit the attached.

Minimal changes:

'To create a unique or primary key constraints on partitioned table'

should be

'To create unique or primary key constraints on partitioned tables'

Erik

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message walther 2022-09-02 10:04:59 Re: Updatable Views and INSERT INTO ... ON CONFLICT
Previous Message Daniel Gustafsson 2022-09-02 09:56:31 Remove dead code from sepgsql