Message-ID: <563e0f91d547c52d7cd2b0d2767290818836f615.camel@cybertec.at>
Subject: Re: Is it possible to log long running recursive/internal
 postgresql queries?
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tom Lane <tgl@sss.pgh.pa.us>, Hotmail <crajac66@hotmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Date: Mon, 20 Feb 2023 14:52:03 +0100
In-Reply-To: <2713826.1676658480@sss.pgh.pa.us>
References: <ddc10360-1072-4e3d-9584-436cdb7d4d82@Spark>
	 <MW4PR11MB6838BAF2DF065F88CD5EE301D7A19@MW4PR11MB6838.namprd11.prod.outlook.com>
	 <2713826.1676658480@sss.pgh.pa.us>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/563e0f91d547c52d7cd2b0d2767290818836f615.camel%40cybertec.at>
Precedence: bulk

On Fri, 2023-02-17 at 13:28 -0500, Tom Lane wrote:
> Hotmail <crajac66@hotmail.com> writes:
> > If it is possible to log long running internal queries as outlined abov=
e any guidance would be appreciated.
>=20
> Either auto_explain or pg_stat_statements could have helped you
> with that, I think.=C2=A0 I believe (without having tested) that if
> configured to track nested statements they would perceive the
> FK enforcement query as a separate statement to track.

Yes, they do.
You need to set "auto_explain.log_nested_statements =3D on" or
"pg_stat_statements.track =3D all".

Yours,
Laurenz Albe