MIME-Version: 1.0
References: <CAAcmDX9t2Od6DmPs3zUq=P2jDFhm-wiVsdF5=+yp=OtsYt1vxQ@mail.gmail.com>
In-Reply-To: <CAAcmDX9t2Od6DmPs3zUq=P2jDFhm-wiVsdF5=+yp=OtsYt1vxQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Tue, 28 Apr 2026 09:05:31 -0700
Message-ID: <CAKFQuwbyRfoacj=OPEt6dmpF3sTiDvZ7ujtVVRXhjhO3vRn24g@mail.gmail.com>
Subject: Re: can recs be transferred between DBs ?
To: dfgpostgres <dfgpostgres3@gmail.com>
Cc: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b0456306508768ab"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwbyRfoacj%3DOPEt6dmpF3sTiDvZ7ujtVVRXhjhO3vRn24g%40mail.gmail.com>
Precedence: bulk

--000000000000b0456306508768ab
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 28, 2026 at 8:56=E2=80=AFAM dfgpostgres <dfgpostgres3@gmail.com=
> wrote:

>
> The managers tell me that they want to restore "beta" back to the main DB=
.
> I know I could do this with something like a perl script, making
> connections to both DBs and transferring them over using select statement=
s
> in "beta_archive" and insert statements in the main DB.  But is there a
> better way, something inherent in PG SQL that allows me to do something
> like this ?
>
>
pg_dump / pg_restore are the core tools at your disposal.  The ability to
specify --inserts and --on-conflict-do-nothing on pg_dump in particular
make at least attempting this against a copy of the backups quite appealing
before trying to write a more targeted transfer script.

David J.

--000000000000b0456306508768ab
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Tue, Apr 28, 2026 at 8:56=E2=80=AFAM dfgpostgres &lt;<a=
 href=3D"mailto:dfgpostgres3@gmail.com">dfgpostgres3@gmail.com</a>&gt; wrot=
e:</span></div></div><div class=3D"gmail_quote gmail_quote_container"><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><span st=
yle=3D"font-family:monospace"><br></span></div><div><span style=3D"font-fam=
ily:monospace">The managers tell me that they want to restore &quot;beta&qu=
ot; back to the main DB.=C2=A0</span></div><div><span style=3D"font-family:=
monospace">I know I could do this with something like a perl script, making=
 connections to both DBs and transferring them over using select statements=
 in &quot;beta_archive&quot; and insert statements in the main DB.=C2=A0 Bu=
t is there a better way, something inherent in PG SQL=C2=A0that allows me t=
o do something like this ?</span></div><div><br></div></div></blockquote><d=
iv><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvet=
ica,sans-serif">pg_dump / pg_restore are the core tools at your disposal.=
=C2=A0 The ability to specify --inserts and --on-conflict-do-nothing on pg_=
dump in particular make at least attempting this against a copy of the back=
ups quite appealing before trying to write a more targeted transfer script.=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,=
helvetica,sans-serif">David J.</div><div class=3D"gmail_default" style=3D"f=
ont-family:arial,helvetica,sans-serif"><br></div></div></div>

--000000000000b0456306508768ab--