On Mon, Apr 22, 2019 at 3:08 PM Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > On 2019-Apr-22, Andres Freund wrote: > > Why is the obvious answer is to not just remove the whole tablespace > > inheritance behaviour? > > Because it was requested by many, and there were plenty of people > surprised that things didn't work that way.
On the other hand, that behavior worked correctly on its own terms, and this behavior seems to be broken, and you've been through a whole series of possible designs trying to figure out how to fix it, and it's still not clear that you've got a working solution. I don't know whether that shows that it is impossible to make this idea work sensibly, but at the very least it proves that the whole area needed a lot more thought than it got before this code was committed (a complaint that I also made at the time, if you recall). "Surprising" is not great, but it is clearly superior to "broken." -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
