On Mon, 2023-01-09 at 16:40 +0100, Laurenz Albe wrote: > > "Using ONLY to add or drop a constraint on only the partitioned table is > > supported as long as there are no partitions. Once partitions exist, using > > ONLY will result in an error. Instead, constraints on the partitions > > themselves can be added and (if they are not present in the parent table) > > dropped." This seems in contradiction to the example involving adding a > > unique constraint while minimizing locking at the bottom of "5.11.2.2. > > Partition Maintenance", which seems to run fine on my local Pg instance: > > > > This technique can be used with UNIQUE and PRIMARY KEY constraints too; the > > indexes are created implicitly when the constraint is created. Example: > > No, that is actually an omission in the documentation. > > The attached patch tries to improve that.
I am sending a reply to the hackers list, so that I can add the patch to the commitfest. Yours, Laurenz Albe
