From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_restore creates public schema? |
Date: | 2022-10-06 17:44:19 |
Message-ID: | da5ad95f-197e-2dcd-ee4d-56af66f90b85@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/6/22 11:48, Christophe Pettus wrote:
>> 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.)
There is, and that is of course the first thing I thought of. Sadly, that VM
doesn't have nearly enough disk space to hold the backup folder. (It's a
tiny 2 CPU, 8GB RAM system with 75GB disk who's only purpose is to
concentrate all the scripts needed to manage 8 servers in one place and
crontab.)
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2022-10-06 17:46:25 | Re: pg_restore creates public schema? |
Previous Message | Christophe Pettus | 2022-10-06 17:32:29 | Re: Replication between Master PostgreSQL database version 9.6.1 and Standby/Slave PostgreSQL database version 10.17. |