From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_restore creates public schema? |
Date: | 2022-10-06 22:01:18 |
Message-ID: | 1399d878-474c-389a-ab88-feeca361560f@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/6/22 2:03 PM, Ron wrote:
> On 10/6/22 14:35, Adrian Klaver wrote:
>> On 10/6/22 09:46, Ron wrote:
>>> On 10/6/22 10:20, Tom Lane 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.
>>
>> 1) So I assume that means Postgres 13.8 has not been installed in
>> anticipation of the change over?
>
> It's certainly been installed on the *new* (RHEL8) server. Not the EOL
> RHEL6 server, because of course the point is to get off of EOL software...
And the RHEL8 server can't talk to the RHEL6 server?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2022-10-06 22:04:47 | Re: pg_restore creates public schema? |
Previous Message | Zheng Li | 2022-10-06 21:30:09 | Re: Support logical replication of DDLs |