Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions - Mailing list pgsql-bugs

From David Rowley
Subject Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
Date
Msg-id CAApHDvqUPNknOz1FELujUFxys67r6eLLH=y-HQf-F=Ni+8e1gQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions  (Bruce Momjian <bruce@momjian.us>)
Responses Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
List pgsql-bugs
On Thu, 7 Sept 2023 at 11:17, Bruce Momjian <bruce@momjian.us> wrote:
>
> On Wed, Sep  6, 2023 at 11:11:05PM +0530, Git Queries wrote:
> > 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.

I can't be certain, but I think the likely reason here is that the
newly restored instance is fine and all indexes match the heap, but
it's the source instance that has indexes with missing entries. Since
the pg_dump queries are most likely to result in seqscans, then all
rows will be returned and the new instance has no missing rows.

David



pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions