Date: Wed, 6 Sep 2023 14:02:19 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Git Queries <gitqueries0@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database
 Migration: Causes and Solutions
Message-ID: <ZPi+q5B58YGDt2+i@momjian.us>
References: <18084-f96f8e0e21fc3bea@postgresql.org>
 <ZPdG3AssVVDTpqtb@momjian.us>
 <CALTThcZtn8fMUUz521yQvp8=czmUn03_uRyNbwOHhmizQyfOHQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CALTThcZtn8fMUUz521yQvp8=czmUn03_uRyNbwOHhmizQyfOHQ@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ZPi%2Bq5B58YGDt2%2Bi%40momjian.us>
Precedence: bulk

On Wed, Sep  6, 2023 at 11:11:05PM +0530, Git Queries wrote:
> > And how did you perform this migration?  pg_dump, pg_upgrade, logical
> > replication?
> 
> Migration was performed using pg_dump.

Uh, that is kind of a surprise since pg_dump/restore does a logical dump
--- none of the binary files are transfered, so it should always be
accurate.

---------------------------------------------------------------------------


> 
> 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?
> 
>     --
>       Bruce Momjian  <bruce@momjian.us>        https://momjian.us
>       EDB                                      https://enterprisedb.com
> 
>       Only you can decide what is important to you.
> 

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.