From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Shaheed Haque <shaheedhaque(at)gmail(dot)com> |
Cc: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch>, postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Scriptable way to validate a pg_dump restore ? |
Date: | 2024-01-29 17:57:00 |
Message-ID: | 7ad098f4-9844-4051-b100-8d3e2292be59@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/29/24 09:28, Shaheed Haque wrote:
>
> Right, for me, state, not just record count is what I'm interested in
> (for the initial full table copy part of replication). So, given the
> explanation about the possible per-table window, is there some property
> of the table that could be used to confirm that a table has made it across?
>
> I guess there is such a thing since the following incremental syncing
> would presumably need it. I had hoped the LSN was this thing, but
> confirmation would be great.
The OP was referring to the pg_dump/pg_restore cycle, you seem to be
referring to logical replication. Is that correct?
>
> Thanks, Shaheed
>
>
> >
> > Thanks !
> >
> > Laura
> >
> >
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Shaheed Haque | 2024-01-29 18:12:17 | Re: Scriptable way to validate a pg_dump restore ? |
Previous Message | Shaheed Haque | 2024-01-29 17:28:32 | Re: Scriptable way to validate a pg_dump restore ? |