On Tue, Nov 6, 2018 at 2:01 PM Simon Riggs <si...@2ndquadrant.com> wrote: > If you can remove the ERROR without any other adverse effects, that sounds > great. > > Please let us know what, if any, adverse effects would be caused so we can > discuss. Thanks
Well, I've already written about this in two previous emails on this thread, so I'm not sure exactly what you think is missing. But to state the problem again: If you don't throw an error when a partition is concurrently detached and then someone routes a tuple to that portion of the key space, what DO you do? Continue inserting tuples into the table even though it's no longer a partition? Throw tuples destined for that partition away? You can make an argument for both of those behaviors, but they're both pretty strange. The first one means that for an arbitrarily long period of time after detaching a partition, the partition may continue to receive inserts that were destined for its former parent. The second one means that your data can disappear into the ether. I don't like either of those things. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
