Re: Logical Decoding and HeapTupleSatisfiesVacuum assumptions - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Logical Decoding and HeapTupleSatisfiesVacuum assumptions
Date
Msg-id CANP8+jL_csweg0oyBUUDj3VAKAVF0emgN9oKHwyR1p2jD1o7SQ@mail.gmail.com
Whole thread Raw
In response to Re: Logical Decoding and HeapTupleSatisfiesVacuum assumptions  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: Logical Decoding and HeapTupleSatisfiesVacuum assumptions
List pgsql-hackers
On 29 January 2018 at 14:13, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote:

> 4) inspect the new row (which we still have in reorderbuffer)
>
> 5) Kabooom! The row has column "c" which we don't see in the catalog.

We don't use caches? Why does a cache miss cause it to explode?

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: PATCH: Exclude unlogged tables from base backups
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] MERGE SQL Statement for PG11