On Fri, Jan 19, 2018 at 2:16 PM, Tomas Vondra
<tomas.vondra@2ndquadrant.com> wrote:
> I think an important piece of this puzzle is that we only really care
> about catalog changes made in a transaction that aborts after doing some
> additional changes, with that catalog tuple in place. Because only then
> we actually need that catalog tuple in order to interpret the changes.
>
> AFAICS that guarantees the catalog changes were not interrupted half-way
> through, leaving some of the catalogs in inconsistent state.
Yeah, that may be true, and I alluded to it in the part you didn't
quote. However, it doesn't help with the second problem I mentioned,
which looks to me to be a fatal problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
