Date: Wed, 7 Sep 2022 09:50:18 +0200
From: Anne Wainwright <anotheranne@fables.co.za>
To: pgsql-novice <pgsql-novice@postgresql.org>
Subject: restore overwrite?
Message-ID: <20220907075018.GA3923@fables.co.za>
Mail-Followup-To: pgsql-novice <pgsql-novice@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Spam_score: 5.9
X-Spam_score_int: 59
X-Spam_bar: +++++
X-Spam_report: Spam detection software,
 running on the system "smtp03.isdsl.net",
 has identified this incoming email as possible spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 The administrator of that system for details.
 Content preview:  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.
 Content analysis details:   (5.9 points, 5.0 required)
  pts rule name              description
 ---- ----------------------
 --------------------------------------------------
  3.6 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
                             [196.210.6.79 listed in zen.spamhaus.org]
  0.0 TVD_RCVD_IP            Message was received from an IP address
  1.1 DATE_IN_PAST_03_06     Date: is 3 to 6 hours before Received: date
  0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
  0.9 SPF_FAIL               SPF: sender does not match SPF record (fail)
 [SPF failed: Please see
 http://www.openspf.org/Why?s=mfrom;id=anotheranne%40fables.co.za;ip=196.210.6.79;r=smtp03.isdsl.net]
  0.0 RCVD_IN_SORBS_DUL      RBL: SORBS: sent directly from dynamic IP
                             address
                             [196.210.6.79 listed in dnsbl.sorbs.net]
 -0.0 T_SCC_BODY_TEXT_LINE   No description available.
  0.4 RDNS_DYNAMIC           Delivered to internal network by host with
                             dynamic-looking rDNS
  0.0 KHOP_HELO_FCRDNS       Relay HELO differs from its IP's reverse DNS
X-Spam-Score: 5.9 (+++++)
X-Spam-Flag: YES
X-Spam-Report: Spam detection software,
 running on the system "smtp03.isdsl.net",
 has identified this incoming email as possible spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 The administrator of that system for details.
 Content preview:  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.
 Content analysis details:   (5.9 points, 5.0 required)
  pts rule name              description
 ---- ----------------------
 --------------------------------------------------
  3.6 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
                             [196.210.6.79 listed in zen.spamhaus.org]
  0.0 TVD_RCVD_IP            Message was received from an IP address
  1.1 DATE_IN_PAST_03_06     Date: is 3 to 6 hours before Received: date
  0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
  0.9 SPF_FAIL               SPF: sender does not match SPF record (fail)
 [SPF failed: Please see
 http://www.openspf.org/Why?s=mfrom;id=anotheranne%40fables.co.za;ip=196.210.6.79;r=smtp03.isdsl.net]
  0.0 RCVD_IN_SORBS_DUL      RBL: SORBS: sent directly from dynamic IP
                             address
                             [196.210.6.79 listed in dnsbl.sorbs.net]
 -0.0 T_SCC_BODY_TEXT_LINE   No description available.
  0.4 RDNS_DYNAMIC           Delivered to internal network by host with
                             dynamic-looking rDNS
  0.0 KHOP_HELO_FCRDNS       Relay HELO differs from its IP's reverse DNS
X-Scan-Signature: 4b55969169a39cf6728b98f2c59236e4{13}}
List-Id: <pgsql-novice.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-novice@lists.postgresql.org>
List-Owner: <mailto:pgsql-novice-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-novice>
Archived-At: 
 <https://www.postgresql.org/message-id/20220907075018.GA3923%40fables.co.za>
Precedence: bulk

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