Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Вложения
- REL15_v13-0001-Fix-catalog-lookup-with-the-wrong-snapshot-durin.patch
- master_v13-0001-Fix-catalog-lookup-with-the-wrong-snapshot-durin.patch
- REL13_v13-0001-Fix-catalog-lookup-with-the-wrong-snapshot-durin.patch
- REL12_v13-0001-Fix-catalog-lookup-with-the-wrong-snapshot-durin.patch
- REL14_v13-0001-Fix-catalog-lookup-with-the-wrong-snapshot-durin.patch
- REL11_v13-0001-Fix-catalog-lookup-with-the-wrong-snapshot-durin.patch
- REL10_v13-0001-Fix-catalog-lookup-with-the-wrong-snapshot-durin.patch
В списке pgsql-hackers по дате отправления:
Предыдущее
От: Kyotaro HoriguchiДата:
Сообщение: Re: Does having pg_last_wal_replay_lsn[replica] >= pg_current_wal_insert_lsn[master] guarantee that the replica is caught up?