| From: | Shaheed Haque <shaheedhaque(at)gmail(dot)com> |
|---|---|
| To: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> |
| Cc: | postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Scriptable way to validate a pg_dump restore ? |
| Date: | 2024-01-29 09:03:48 |
| Message-ID: | CAHAc2jedUotr6ge45daYpd0p2rRFMb4W2XjNGO1usq4oT5qSeA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I'd also like to know how to do this. The current approaches seem, afaict,
to involve making on both end of the connection. Even given the inherently
racy nature of the issue, that seems unwieldy to me.
On Mon, 29 Jan 2024, 14:12 Laura Smith, <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch>
wrote:
> Hi
>
> Let's say I've got a scenario where I'm doing a pg_dump replication rather
> than online streaming, e.g. due to air-gap or whatever.
>
> Is there a scriptable way to validate the restore ? e.g. using doing
> something clever with ctid or something to ensure both the schema and all
> its rows were restored to the same point at which the dump was taken ?
>
> Thanks !
>
> Laura
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-01-29 09:06:07 | Re: Scriptable way to validate a pg_dump restore ? |
| Previous Message | Laura Smith | 2024-01-29 08:12:17 | Scriptable way to validate a pg_dump restore ? |