<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.delftsolutions.nl/index.php?action=history&amp;feed=atom&amp;title=Postgres_issues</id>
	<title>Postgres issues - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://docs.delftsolutions.nl/index.php?action=history&amp;feed=atom&amp;title=Postgres_issues"/>
	<link rel="alternate" type="text/html" href="https://docs.delftsolutions.nl/index.php?title=Postgres_issues&amp;action=history"/>
	<updated>2026-04-03T22:08:26Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://docs.delftsolutions.nl/index.php?title=Postgres_issues&amp;diff=698&amp;oldid=prev</id>
		<title>Vincent: Created page with &quot;&#039;&#039;WIP&#039;&#039;  When you suspect database/postgres issues causing degraded performance on a service, you can check the following:  == Check blocking sessions ==  A function listing the sessions preventing a session from acquiring a lock  - https://pgpedia.info/p/pg_blocking_pids.html  == Lock monitoring ==  Viewing information on current locking state  - https://wiki.postgresql.org/wiki/Lock_Monitoring  == Postgres logging ==  Options for logging locking issues in postgres  - h...&quot;</title>
		<link rel="alternate" type="text/html" href="https://docs.delftsolutions.nl/index.php?title=Postgres_issues&amp;diff=698&amp;oldid=prev"/>
		<updated>2026-03-24T15:45:54Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;&amp;#039;&amp;#039;WIP&amp;#039;&amp;#039;  When you suspect database/postgres issues causing degraded performance on a service, you can check the following:  == Check blocking sessions ==  A function listing the sessions preventing a session from acquiring a lock  - https://pgpedia.info/p/pg_blocking_pids.html  == Lock monitoring ==  Viewing information on current locking state  - https://wiki.postgresql.org/wiki/Lock_Monitoring  == Postgres logging ==  Options for logging locking issues in postgres  - h...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;WIP&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
When you suspect database/postgres issues causing degraded performance on a service, you can check the following:&lt;br /&gt;
&lt;br /&gt;
== Check blocking sessions ==&lt;br /&gt;
&lt;br /&gt;
A function listing the sessions preventing a session from acquiring a lock&lt;br /&gt;
&lt;br /&gt;
- https://pgpedia.info/p/pg_blocking_pids.html&lt;br /&gt;
&lt;br /&gt;
== Lock monitoring ==&lt;br /&gt;
&lt;br /&gt;
Viewing information on current locking state&lt;br /&gt;
&lt;br /&gt;
- https://wiki.postgresql.org/wiki/Lock_Monitoring&lt;br /&gt;
&lt;br /&gt;
== Postgres logging ==&lt;br /&gt;
&lt;br /&gt;
Options for logging locking issues in postgres&lt;br /&gt;
&lt;br /&gt;
- https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-LOCK-WAITS&lt;/div&gt;</summary>
		<author><name>Vincent</name></author>
	</entry>
</feed>