> And how did you perform this migration? pg_dump, pg_upgrade, logical > replication?
Migration was performed using pg_dump.
On Tue, Sep 5, 2023 at 8:48 PM Bruce Momjian <bruce@momjian.us> wrote:
On Mon, Sep 4, 2023 at 05:55:51PM +0000, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 18084 > Logged by: Git Queries > Email address: gitqueries0@gmail.com > PostgreSQL version: Unsupported/Unknown > Operating system: Microsoft Windows Server 2019 Standard > Description: > > Version - PostgreSQL 10.20, compiled by Visual C++ build 1800, 64-bit > > Platform - Windows > > Regarding PostgreSQL, during the migration from PG 10.20 to 14.7, we will > perform a sanity check on the migrated tables using source and destination > row counts. Occasionally, we encounter count mismatches where the source > database has fewer rows, resulting in a higher count, or more rows, > resulting in a lower count. > > Note: There are no migration issues, as all data rows have been successfully > migrated without data loss.
And how did you perform this migration? pg_dump, pg_upgrade, logical replication?
