MIME-Version: 1.0
In-Reply-To: <20220907075018.GA3923@fables.co.za>
References: <20220907075018.GA3923@fables.co.za>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 7 Sep 2022 09:31:11 -0700
Message-ID: 
 <CAKFQuwZkmTAv-7_3cof5phaMqhfdTnWHVs+v-LssN=iF6O1QOA@mail.gmail.com>
Subject: Re: restore overwrite?
To: pgsql-novice <pgsql-novice@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000046d66005e818d709"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwZkmTAv-7_3cof5phaMqhfdTnWHVs%2Bv-LssN%3DiF6O1QOA%40mail.gmail.com>
Precedence: bulk

--00000000000046d66005e818d709
Content-Type: text/plain; charset="UTF-8"

On Wednesday, September 7, 2022, Anne Wainwright <anotheranne@fables.co.za>
wrote:

> Hi,
>
> I want to do a restore to write over the top of existing data.
>
> The unique key prevents this. Should I rather TRUNCATE the tables
> concerned before the restore? That is a bit scary if the restore does
> not work. Is there a better way.
>
> (This data on v.8.4.4 which is being moved to latest version 14).
>
> Thanks for answer in advance
>
> Anne
>
>
If you cannot just do a simple restore into an empty v14 database you are
probably better off not thinking of this as a restore operation but instead
an ETL operation and write ETL code to extract data from the v8 database,
do any necessary transforms (possibly within the v14 database but within a
staging table), then merge the transformed data into the real v14 tables.

David J.

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

<br><br>On Wednesday, September 7, 2022, Anne Wainwright &lt;<a href=3D"mai=
lto:anotheranne@fables.co.za">anotheranne@fables.co.za</a>&gt; wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">Hi,<br>
<br>
I want to do a restore to write over the top of existing data.<br>
<br>
The unique key prevents this. Should I rather TRUNCATE the tables<br>
concerned before the restore? That is a bit scary if the restore does<br>
not work. Is there a better way.<br>
<br>
(This data on v.8.4.4 which is being moved to latest version 14).<br>
<br>
Thanks for answer in advance<br>
<br>
Anne<br><br>
</blockquote><div><br></div><div>If you cannot just do a simple restore int=
o an empty v14 database you are probably better off not thinking of this as=
 a restore operation but instead an ETL operation and write ETL code to ext=
ract data from the v8 database, do any necessary transforms (possibly withi=
n the v14 database but within a staging table), then merge the transformed =
data into the real v14 tables.</div><div><br></div><div>David J.</div><div>=
=C2=A0</div>

--00000000000046d66005e818d709--