Re: Backup and Restore (pg_dump & pg_restore)

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Backup and Restore (pg_dump & pg_restore)
Date: 2019-04-21 22:13:23
Message-ID: 7c503445-2da0-db3c-5345-e814b6ce97f9@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

On 4/21/19 2:20 PM, Ron wrote:

>> I see this sort of thing in monitoring systems e.g. environmental
>> controls all the time. Things get flagged because they wander over set
>> points intermittently. It is technically an error but unless they stay
>> over the line it is just another data point.
>
> Errors need to be fixed.  If the restore can proceed without harm, then
> it's an Informational message.

That is a choice thing:

https://www.postgresql.org/docs/11/app-pgrestore.html

"
-e
--exit-on-error

Exit if an error is encountered while sending SQL commands to the
database. The default is to continue and to display a count of errors at
the end of the restoration.
"

It is also one of those eye of the beholder things as evidenced by:

https://www.postgresql.org/docs/11/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT

Severity Usage syslog eventlog
...
ERROR Reports an error ... WARNING ERROR
...

Edited to keep on one line.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2019-04-21 22:25:29 Re: Display View Columns and Their Source Tables and Columns
Previous Message legrand legrand 2019-04-21 21:51:44 Re: Display View Columns and Their Source Tables and Columns

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2019-04-21 23:07:53 Re: Out of Memory errors are frustrating as heck!
Previous Message Ron 2019-04-21 21:20:03 Re: Backup and Restore (pg_dump & pg_restore)