Re: [BUG] Incorrect historic snapshot may be serialized to disk during fast-forwarding

From: cca5507 <cca5507(at)qq(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, ocean_li_996 <ocean_li_996(at)163(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG] Incorrect historic snapshot may be serialized to disk during fast-forwarding
Date: 2026-01-17 15:56:17
Message-ID: tencent_DC9D5A685F215A6D57CA8D0C031EE6C18506@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

The commit message of 'user_catalog_table' says:

```
Replication solutions built around the logical decoding machinery
will likely need to set this operation for their configuration
tables; it might also be needed by extensions which perform table
access in their output functions.
```

So if there is an extension using the incorrect snapshot to scan user
catalog tables, it will get the wrong result, right?

--
Regards,
ChangAo Chen

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Andrey Silitskiy 2026-01-17 15:46:24 Re: Exit walsender before confirming remote flush in logical replication