Date: Fri, 13 Dec 2024 11:26:37 -0800 (PST)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general@postgresql.org
Subject: Re: Restoring database from backup
In-Reply-To: <f66398c1-e8b6-49d6-b893-c2c0125b0e2c@aklaver.com>
Message-ID: <c277f544-7982-8d2d-8242-c7b543ae2191@appl-ecosys.com>
References: <d97a8613-3b55-4a5b-887f-db7d2923c4ab@appl-ecosys.com> <3745bd88-413f-4fa5-90a1-d374852d10a9@aklaver.com> <f4612ca2-7495-ab56-65cc-cd289e16da77@appl-ecosys.com> <f66398c1-e8b6-49d6-b893-c2c0125b0e2c@aklaver.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://www.postgresql.org/message-id/c277f544-7982-8d2d-8242-c7b543ae2191%40appl-ecosys.com>
Precedence: bulk

On Fri, 13 Dec 2024, Adrian Klaver wrote:

> Alright, from here:
>
> https://www.postgresql.org/docs/current/app-pgdump.html
>
> "-c
> --clean
>
>    Output commands to DROP all the dumped database objects prior to 
> outputting the commands for creating them. This option is useful when the 
> restore is to overwrite an existing database. If any of the objects do not 
> exist in the destination database, ignorable error messages will be reported 
> during restore, unless --if-exists is also specified.
>
>    This option is ignored when emitting an archive (non-text) output file. 
> For the archive formats, you can specify the option when you call pg_restore.
> "
>
> This means when you run the script with:
>
> psql -d bustrac -f bustrac-2024-12-12.sql
>
> it will clean out the current corrupted objects and replace them with those 
> in the backup file.

Adrian,

That's what I thought since I wrote the script based on reading pgdump a
long time ago.

Thanks for confirming! I'll fix my carelessness now.

Carpe weekend,

Rich