MIME-Version: 1.0
References: <00c201db6c13$7a1fbb80$6e5f3280$@msym.fr>
In-Reply-To: <00c201db6c13$7a1fbb80$6e5f3280$@msym.fr>
From: Jeff Janes <jeff.janes@gmail.com>
Date: Tue, 21 Jan 2025 22:15:19 -0500
Message-ID: 
 <CAMkU=1xhQfTfD+9HvumZVF1QeMZcj9HX3itctxDa=1gBY7SUng@mail.gmail.com>
Subject: Re: Commit with wait event on advisory lock!
To: msalais@msym.fr
Cc: pgsql-admin@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000000b92f062c42e804"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMkU%3D1xhQfTfD%2B9HvumZVF1QeMZcj9HX3itctxDa%3D1gBY7SUng%40mail.gmail.com>
Precedence: bulk

--00000000000000b92f062c42e804
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 21, 2025 at 9:48=E2=80=AFAM <msalais@msym.fr> wrote:

> Hi all,
>
>
>
> I have long commits on a production database. To know why this happens I
> organized a snapshot system on table pg_stat_activity.
>
> When I check the result I have this row in it:
>
>
>
> postgres=3D# select * from public.fdj_ms_slow_stmts where pid =3D 2285947=
 \gx
>

What is the full version()?  What is the query used to populate this
snapshot table?  Are the advisory locks being used as session-level locks
or transaction-level locks?

Cheers,

Jeff

--00000000000000b92f062c42e804
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Jan 21, 2025 at 9:48=E2=80=AFAM &=
lt;<a href=3D"mailto:msalais@msym.fr">msalais@msym.fr</a>&gt; wrote:</div><=
div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div class=3D"msg-1916708514449136891"><div lang=3D"=
FR" style=3D"overflow-wrap: break-word;"><div class=3D"m_-19167085144491368=
91WordSection1"><p class=3D"MsoNormal">Hi all,<u></u><u></u></p><p class=3D=
"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal"><span lang=3D"EN=
-US">I have long commits on a production database. To know why this happens=
 I organized a snapshot system on table pg_stat_activity.<u></u><u></u></sp=
an></p><p class=3D"MsoNormal"><span lang=3D"EN-US">When I check the result =
I have this row in it:<u></u><u></u></span></p><p class=3D"MsoNormal"><span=
 lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span=
 lang=3D"EN-US" style=3D"font-family:Consolas">postgres=3D# select * from p=
ublic.fdj_ms_slow_stmts where pid =3D 2285947 \gx</span></p></div></div></d=
iv></blockquote><div><br></div><div>What is the full version()?=C2=A0 What =
is the query used to populate this snapshot table?=C2=A0 Are the advisory l=
ocks being used as session-level locks or transaction-level locks?</div><di=
v><br></div><div>Cheers,</div><div><br></div><div>Jeff</div></div></div>

--00000000000000b92f062c42e804--