Re: Postgres Partitions Limitations (5.11.2.3)
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: navbarry@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2023-12-04T20:10:05Z
Lists: pgsql-hackers, pgsql-docs
Attachments
- 0001-Doc-Fix-omission-in-partitioning-limitations.V2.patch (text/x-patch) patch 0001
On Fri, 2023-12-01 at 18:49 +0530, Ashutosh Bapat wrote: > On Thu, Nov 30, 2023 at 10:29 PM Laurenz Albe <laurenz.albe@cybertec.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? Yours, Laurenz Albe
Commits
-
Fix omission in partitioning limitation documentation
- 18d51c0bb190 12.18 landed
- 9a94e9ae7ea2 13.14 landed
- 5b0287adcab3 14.11 landed
- bcaf41c608b1 15.6 landed
- af36f1993da1 16.2 landed
- ba2d2784f3f8 17.0 landed