Re: Error for WITH options on partitioned tables

From: Japin Li <japinli(at)hotmail(dot)com>
To: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Error for WITH options on partitioned tables
Date: 2022-09-16 12:48:37
Message-ID: MEYP282MB166990F77DAABF1BE9D5AB64B6489@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Fri, 16 Sep 2022 at 20:13, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> wrote:
> Someone on general list recently complained that the error message
> from trying to use options on a partitioned table was misleading,
> which it definitely is:
>
> CREATE TABLE parted_col_comment (a int, b text) PARTITION BY LIST (a)
> WITH (fillfactor=100);
> ERROR: unrecognized parameter "fillfactor"
>
> Which is verified by patch 001.
>
> Patch 002 replaces this with a more meaningful error message, which
> matches our fine manual.
> https://www.postgresql.org/docs/current/sql-createtable.html
>
> ERROR: cannot specify storage options for a partitioned table
> HINT: specify storage options on leaf partitions instead

Looks good. Does this means we don't need the partitioned_table_reloptions()
function and remove the reloptions validation in DefineRelation() for
partitioned table. Or we can ereport() in partitioned_table_reloptions().

--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-09-16 12:51:40 Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work.
Previous Message Simon Riggs 2022-09-16 12:33:23 Pruning never visible changes