> On Nov 17, 2020, at 11:44 AM, Bruce Momjian wrote:
>
> On Tue, Nov 17, 2020 at 11:59:10AM -0500, Jeremy Wilson wrote:
>> pg_restore: WARNING: terminating connection because of crash of another
>> server process
>> DETAIL: The postmaster has commanded this server process to roll back the
>
On Tue, Nov 17, 2020 at 02:44:47PM -0500, Bruce Momjian wrote:
> On Tue, Nov 17, 2020 at 11:59:10AM -0500, Jeremy Wilson wrote:
> > pg_restore: WARNING: terminating connection because of crash of another
> > server process
> > DETAIL: The postmaster has commanded this server process to roll back
On Tue, Nov 17, 2020 at 11:59:10AM -0500, Jeremy Wilson wrote:
> pg_restore: WARNING: terminating connection because of crash of another
> server process
> DETAIL: The postmaster has commanded this server process to roll back the
> current transaction and exit, because another server process ex
> On Nov 17, 2020, at 12:18 PM, Adrian Klaver wrote:
>
> On 11/17/20 8:59 AM, Jeremy Wilson wrote:
>
> Was this after a clean install of the corrected RPM’s?
Yes, this is a fresh install of CentOS 8 and installed using the updated repo
and RPMs.
On 11/17/20 8:59 AM, Jeremy Wilson wrote:
I’m continuing my upgrade journey, this time from 11 to 13, and the process is
dying in the copy phase, always on the same DB:
—
Performing Upgrade
--
Analyzing all rows in the new cluster ok
Freezing all rows in th
I’m continuing my upgrade journey, this time from 11 to 13, and the process is
dying in the copy phase, always on the same DB:
—
Performing Upgrade
--
Analyzing all rows in the new cluster ok
Freezing all rows in the new clusterok
Dele
