Re: ALTER TABLE .. DETACH PARTITION CONCURRENTLY
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Amit Langote <amitlangote09@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2021-03-21T19:15:19Z
Lists: pgsql-hackers
On Sun, Mar 21, 2021 at 01:14:20PM -0500, Justin Pryzby wrote: > On Sun, Mar 21, 2021 at 03:01:15PM -0300, Alvaro Herrera wrote: > > > But note that it doesn't check if an existing constraint "implies" the new > > > constraint - maybe it should. > > > > Hm, I'm not sure I want to do that, because that means that if I later > > have to attach the partition again with the same partition bounds, then > > I might have to incur a scan to recheck the constraint. I think we want > > to make the new constraint be as tight as possible ... > > The ATTACH PARTITION checks if any existing constraint impilies the (proposed) > partition bounds, not just if constraints are equal. So I'm suggesting to do > the same here. On Sun, Mar 21, 2021 at 04:07:12PM -0300, Alvaro Herrera wrote: > On 2021-Mar-21, Justin Pryzby wrote: > > On Sun, Mar 21, 2021 at 03:22:00PM -0300, Alvaro Herrera wrote: > > > So if we do that on DETACH, what would happen on ATTACH? > > > > Do you mean what happens to the constraint that was already there ? > > Nothing, since it's not ours to mess with. Checking ImpliedBy() rather than > > equal() doesn't change that. > > No, I meant what happens regarding checking existing values in the > table: is the table scanned even if the partition constraint is implied > by existing table constraints? I'm still not sure we're talking about the same thing. Your patch adds a CHECK constraint during DETACH CONCURRENTLY, and I suggested that it should avoid adding it if it's redundant with an existing constraint, even if not equal(). The current behavior (since v10) is this: postgres=# ALTER TABLE p ATTACH PARTITION p1 FOR VALUES FROM (1)TO(2); DEBUG: partition constraint for table "p1" is implied by existing constraints ALTER TABLE And that wouldn't change, except the CHECK constraint would be added automatically during detach (if it wasn't already implied). Maybe the CHECK constraint should be added without CONCURRENTLY, too. One fewer difference in behavior. -- Justin
Commits
-
Make detach-partition-concurrently-4 less timing sensitive
- eb43bdbf5104 14.0 landed
-
Improve documentation on DETACH PARTITION lock levels
- db6e1aeb952e 14.0 landed
-
Track detached partitions more accurately in partdescs
- 3fe773b14975 14.0 landed
-
Allow a partdesc-omitting-partitions to be cached
- d6b8d29419df 14.0 landed
-
Fix relcache inconsistency hazard in partition detach
- 8aba9322511f 14.0 landed
-
Don't add a redundant constraint when detaching a partition
- 7b357cc6ae55 14.0 landed
-
ALTER TABLE ... DETACH PARTITION ... CONCURRENTLY
- 71f4c8c6f74b 14.0 landed
-
Let ALTER TABLE Phase 2 routines manage the relation pointer
- cd03c6e94b09 14.0 landed
-
Check default partitions constraints while descending
- f481d2823297 14.0 landed
- ef1e1250e716 12.5 landed
- d0230a43fcae 13.0 landed