I went looking in the postgres code and took it more as a "Feature request" where if the index building / table scanning, etc is interrupted for concurrent buil

I went looking in the postgres code and took it more as a "Feature request" where if the index building / table scanning, etc is interrupted for concurrent builds, PG could drop the index in the end. I can see how PG keeps it around however, since invalid indexes can be useful for administrators. However, for application developers - unless you are familiar with the internals, this comes off as a big surprise. Would love to learn more from folks who are more familiar with the internals.