Search Postgresql Archives

Re: Table update: restore or replace?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Table update: restore or replace?
From: Rich Shepard <rshepard@xxxxxxxxxxxxxxx>
Date: Tue, 14 May 2019 13:59:18 -0700 (PDT)
In-reply-to: <5fb66fe3-0aa0-3d6d-db53-172a6c3f1a30@aklaver.com>
References: <alpine.LNX.2.20.1905141341311.30120@salmo.appl-ecosys.com> <5fb66fe3-0aa0-3d6d-db53-172a6c3f1a30@aklaver.com>
User-agent: Alpine 2.20 (LNX 67 2015-01-07)

On Tue, 14 May 2019, Adrian Klaver wrote:

A file level backup or database dump?


Adrian,

File level. April 20th is my most recent database dump because I forgot to
run it last Friday afternoon.

Rich

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Table update: restore or replace?
  - From: Ron
- Re: Table update: restore or replace?
  - From: Adrian Klaver

References:
- Table update: restore or replace?
  - From: Rich Shepard
- Re: Table update: restore or replace?
  - From: Adrian Klaver

Prev by Date: Re: Table update: restore or replace?
Next by Date: Re: Table update: restore or replace?
Previous by thread: Re: Table update: restore or replace?
Next by thread: Re: Table update: restore or replace?
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux