From: | Wasim Devale <wasimd60(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |
Date: | 2024-08-15 03:54:01 |
Message-ID: | CAB5fag4XgMpsFWM1N=B4m4uGkMBkgRK5-LYUEgsvAFZ0OxBjBg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Scott
I do reindexing on database when production is completely down. it's only
the application UI queries that holds the tables.
I will dig down more if require your help I will post it.
Thanks David,
Thanks Scott.
On Thu, 15 Aug, 2024, 9:15 am Scott Ribe, <scott_ribe(at)elevated-dev(dot)com>
wrote:
> Given errors like the pair you posted, my next step would be to examine
> the queries being executed by those processes during the deadlock. Now, I
> think by the time the deadlock error is logged, the queries involved have
> been cancelled, so it's possible the processes have gone on to another
> query and so pg_stat_activity might not have useful information, or it
> might--depending on what your app would do after a deadlock error.
>
> If it does not, then the next thing would be to set
> log_min_duration_statement to less than deadlock/statement timeout, so that
> you could look through logs to figure out what are the two queries which
> are deadlocking against each other.
>
> --
> Scott Ribe
> scott_ribe(at)elevated-dev(dot)com
> https://www.linkedin.com/in/scottribe/
>
>
>
> > On Aug 14, 2024, at 9:38 PM, Wasim Devale <wasimd60(at)gmail(dot)com> wrote:
> >
> > Ok thanks for the insights.
> > Do we need to do any config changes in the config file?
> > We have also configured Datadog agent at operating system level that
> checks postgresql activity it's has the pgpouncer.d config file that is
> unchanged after the migration. This might be the possible reason that it is
> throughing dead lock error.
> > Please through some insights on the above.
> > Thanks for the immediate help.
> > Regards,
> > Wasim
> >
> > On Thu, 15 Aug, 2024, 9:01 am David G. Johnston, <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> > On Wednesday, August 14, 2024, Wasim Devale <wasimd60(at)gmail(dot)com> wrote:
> > So it's not a postgresql issue. It's from the application side correct?
> >
> > That’s the assumption. The vast majority of locks happen because the
> “application” executed SQL commands.
> >
> > David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-08-15 04:08:28 | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |
Previous Message | David G. Johnston | 2024-08-15 03:50:44 | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |