Re: pg_restore creates public schema?

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore creates public schema?
Date: 2022-10-06 16:48:11
Message-ID: 5454C60C-EBBC-4A96-9497-667EAB87907D@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Oct 6, 2022, at 09:46, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> Because installing new software on production servers requires hurdles (Service Now change ticket approved by the application support manager, Delivery Service Manager, Engineering Change Board, and a one week lead time before installing during the Saturday night maintenance window) that I'm not willing to jump through just to take an ad hoc database backup.

Running the new pg_dump doesn't require that it be installed on the server, just that it have access to it. (I understand there may be access restrictions that make that inconvenient as well, but presumably *some* servers have access to 5432 and can be used to run pg_dump.)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2022-10-06 17:16:01 Re: Support logical replication of DDLs
Previous Message Ron 2022-10-06 16:46:26 Re: pg_restore creates public schema?