Hello Julien,
The procedure for doing the upgrade is different for AWS.
After the PG upgrade we can see many locks in our system we believe this is
the main reason for the issue we are facing,
I can see these locks when using pg_stat_activity.
Along with that few queries which were executing
Once again, please don't top post.
On Sat, Apr 04, 2020 at 11:57:02AM +0530, Tejaswini GC wrote:
> Hello Julien,
>
> The procedure for doing the upgrade is different for AWS.
>
And is it possible to know what the procedure was?
>
> After the PG upgrade we can see many locks in our system
Hello Julien,
Thanks for your inputs,
I shall get back to you If some information is needed.
*Regards*
*Tejaswini G C*
*IT Retail Team*
On Thu, Apr 2, 2020 at 4:35 PM Julien Rouhaud wrote:
> Please don't top-post, it makes it hard to follow the discussion.
>
> On Thu, Apr 02, 2020 at
Please don't top-post, it makes it hard to follow the discussion.
On Thu, Apr 02, 2020 at 03:52:56PM +0530, Tejaswini GC wrote:
>
> I'm in touch with our hosting team to get more information for your queries.
> As of now I can share these details.
> We did analyze on the DB, but not the vacuum,
Hello Julien,
Thanks for your response.
I'm in touch with our hosting team to get more information for your queries.
As of now I can share these details.
We did analyze on the DB, but not the vacuum,
We are using AWS RDS.
Please help me with these queries as well.
1) Will the process change if
Hi,
On Thu, Apr 02, 2020 at 03:52:25AM +, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16334
> Logged by: Tejaswini GC
> Email address: tejaswini...@decathlon.com
> PostgreSQL version: 10.10
> Operating system:
