Re: Help diagnosing replication (copy) error

From: Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com>
To: Jeff Ross <jross(at)openvistas(dot)net>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Help diagnosing replication (copy) error
Date: 2024-03-09 06:26:16
Message-ID: CAKE1AibagztV0cqU1o+ePqxgV3wfy3mjFchYArO-zdvSdmjboQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Mar 9, 2024 at 11:06 AM Jeff Ross <jross(at)openvistas(dot)net> wrote:

>
> RDS is a black box--who knows what's really going on there? It would be
> interesting to see what the response is after you open a support case.
> I hope you'll be able to share that with the list.
>
> This is very mysterious. I logged the case, and before it had been picked
up by an analyst, the issue somehow resolved itself without me doing
anything.

I now have 418M+ rows in the table that it got stuck on.

:shrug:

Thanks Adrian and Jeff for responding.

Steve

> Jeff
>
>
>
>
>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message omkar narkar 2024-03-09 08:33:39 Getting error while upgrading
Previous Message hassan rafi 2024-03-09 04:19:07 Seeing high query planning time on Azure Postgres Single Server version 11.