LWN: Comments on "Declarative partitioning in PostgreSQL" https://lwn.net/Articles/965508/ This is a special feed containing comments posted to the individual LWN article titled "Declarative partitioning in PostgreSQL". en-us Mon, 20 Oct 2025 21:42:08 +0000 Mon, 20 Oct 2025 21:42:08 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Declarative partitioning in PostgreSQL https://lwn.net/Articles/969568/ https://lwn.net/Articles/969568/ daroc <div class="FormattedComment"> I don't believe partitions can span separate hosts; although I don't recall the question coming up at the time, so perhaps I am mistaken. I think the fundamental problem would be having some way to introduce consistent constraints across separate instances of PostgreSQL, which sounds hard.<br> </div> Fri, 12 Apr 2024 13:06:41 +0000 Declarative partitioning in PostgreSQL https://lwn.net/Articles/969538/ https://lwn.net/Articles/969538/ grifferz <div class="FormattedComment"> With either the old or the new method, can partitioned tables span multiple hosts, or does that kind of partitioning still have to be done entirely in the client logic?<br> </div> Thu, 11 Apr 2024 22:18:38 +0000 Declarative partitioning in PostgreSQL https://lwn.net/Articles/967085/ https://lwn.net/Articles/967085/ mirabilos <div class="FormattedComment"> How can this be called nearly feature-complete when whole-partitioned-table indexes (necessary for constraints) are still not even on the horizon?<br> <p> As to the names… ouch, yes, hadn’t thought about that. Is it possible to make it so all child tables go into a separate schema (one schema per parent table) as kind of namespacing?<br> </div> Fri, 29 Mar 2024 06:28:10 +0000