| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Nikhil Sontakke <nikhils(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical Decoding and HeapTupleSatisfiesVacuum assumptions |
| Date: | 2018-01-19 19:33:52 |
| Message-ID: | CA+TgmoZCJgEsgdcBhN6ObDEEnaE9xXp+P-3wq8yk9c1FgaGKaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 19, 2018 at 2:16 PM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-01-19 19:54:25 | Re: [HACKERS] Refactor handling of database attributes between pg_dump and pg_dumpall |
| Previous Message | Tomas Vondra | 2018-01-19 19:16:46 | Re: Logical Decoding and HeapTupleSatisfiesVacuum assumptions |