Re: Postgres Partitions Limitations (

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: navbarry(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres Partitions Limitations (
Date: 2023-12-04 20:10:05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-docs pgsql-hackers

On Fri, 2023-12-01 at 18:49 +0530, Ashutosh Bapat wrote:
> On Thu, Nov 30, 2023 at 10:29 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> >
> > On Thu, 2023-11-30 at 19:22 +0530, Ashutosh Bapat wrote:
> > > May be attach the patch to hackers thread (this) as well?
> >
> > If you want, sure.  I thought it was good enough if the thread
> > is accessible via the commitfest app.
> The addition is long enough that it deserved to be outside of parentheses.
> I think it's worth mentioning the exception but in a way that avoids
> repeating what's mentioned in the last paragraph of just the previous
> section. I don't have brilliant ideas about how to rephrase it.
> Maybe "Using ONLY to add or drop a constraint, other than PRIMARY and
> UNIQUE, on only the partitioned table is supported as long as there
> are no partitions. ...".

I agree that the parenthesis is too long. I shortened it in the attached
patch. Is that acceptable?

Laurenz Albe

Attachment Content-Type Size
0001-Doc-Fix-omission-in-partitioning-limitations.V2.patch text/x-patch 1.5 KB

In response to


Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2023-12-04 20:28:53 Missing "CONSTRAINT" keyword in ADD CONSTRAINT form?
Previous Message Michael Paquier 2023-12-03 23:11:40 Re: Delete description of trigger file

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-12-04 20:10:25 Re: meson: Stop using deprecated way getting path of files
Previous Message Andrew Dunstan 2023-12-04 20:06:31 Re: Emitting JSON to file using COPY TO