<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>pg_terminate_backend &#8211; Database Research &amp; Development</title>
	<atom:link href="https://www.dbrnd.com/tag/pg_terminate_backend/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dbrnd.com</link>
	<description>BIGData &#124; NoSQL &#124; MSSQL &#124; MySQL &#124; PostgreSQL</description>
	<lastBuildDate>Sat, 28 Jan 2017 03:45:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.6</generator>
	<item>
		<title>PostgreSQL: Must know about pg_terminate_backend and pg_cancel_backend before killing to any session</title>
		<link>https://www.dbrnd.com/2017/01/postgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process/</link>
		
		<dc:creator><![CDATA[Anvesh Patel]]></dc:creator>
		<pubDate>Thu, 26 Jan 2017 03:40:49 +0000</pubDate>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[Anvesh Patel]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[database research and development]]></category>
		<category><![CDATA[dbrnd]]></category>
		<category><![CDATA[kill]]></category>
		<category><![CDATA[kill session]]></category>
		<category><![CDATA[long running queries]]></category>
		<category><![CDATA[pg_cancel_backend]]></category>
		<category><![CDATA[pg_terminate_backend]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[Postgres Query]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[PostgreSQL Administrator]]></category>
		<category><![CDATA[PostgreSQL Error]]></category>
		<category><![CDATA[PostgreSQL Monitoring]]></category>
		<category><![CDATA[PostgreSQL Performance Tuning]]></category>
		<category><![CDATA[PostgreSQL Programming]]></category>
		<category><![CDATA[PostgreSQL Tips and Tricks]]></category>
		<guid isPermaLink="false">https://www.dbrnd.com/?p=4400</guid>

					<description><![CDATA[I had shared one article about, how to kill all running connections of PostgreSQL Database. PostgreSQL: Script to Kill all Running Connections and Sessions of a Database In this post, I am sharing small, but a very important note on PostgreSQL pg_terminate_backend and pg_cancel_backend which are used to kill the running query or session. pg_cancel_backend(): [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2017%2F01%2Fpostgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process%2F&amp;linkname=PostgreSQL%3A%20Must%20know%20about%20pg_terminate_backend%20and%20pg_cancel_backend%20before%20killing%20to%20any%20session" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2017%2F01%2Fpostgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process%2F&amp;linkname=PostgreSQL%3A%20Must%20know%20about%20pg_terminate_backend%20and%20pg_cancel_backend%20before%20killing%20to%20any%20session" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2017%2F01%2Fpostgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process%2F&amp;linkname=PostgreSQL%3A%20Must%20know%20about%20pg_terminate_backend%20and%20pg_cancel_backend%20before%20killing%20to%20any%20session" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_pinterest" href="https://www.addtoany.com/add_to/pinterest?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2017%2F01%2Fpostgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process%2F&amp;linkname=PostgreSQL%3A%20Must%20know%20about%20pg_terminate_backend%20and%20pg_cancel_backend%20before%20killing%20to%20any%20session" title="Pinterest" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2017%2F01%2Fpostgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process%2F&amp;linkname=PostgreSQL%3A%20Must%20know%20about%20pg_terminate_backend%20and%20pg_cancel_backend%20before%20killing%20to%20any%20session" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_pocket" href="https://www.addtoany.com/add_to/pocket?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2017%2F01%2Fpostgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process%2F&amp;linkname=PostgreSQL%3A%20Must%20know%20about%20pg_terminate_backend%20and%20pg_cancel_backend%20before%20killing%20to%20any%20session" title="Pocket" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.dbrnd.com%2F2017%2F01%2Fpostgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process%2F&#038;title=PostgreSQL%3A%20Must%20know%20about%20pg_terminate_backend%20and%20pg_cancel_backend%20before%20killing%20to%20any%20session" data-a2a-url="https://www.dbrnd.com/2017/01/postgresql-must-know-about-pg_terminate_backend-and-pg_cancel_backend-before-killing-to-any-session-query-process/" data-a2a-title="PostgreSQL: Must know about pg_terminate_backend and pg_cancel_backend before killing to any session"></a></p><p>I had shared one article about, how to kill all running connections of PostgreSQL Database.</p>
<blockquote class="wp-embedded-content" data-secret="dPOYCiCYoq"><p><a href="https://www.dbrnd.com/2015/11/postgresql-script-to-kill-all-running-connections-and-sessions-of-a-database/">PostgreSQL: Script to Kill all Running Connections and Sessions of a Database</a></p></blockquote>
<p><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  src="https://www.dbrnd.com/2015/11/postgresql-script-to-kill-all-running-connections-and-sessions-of-a-database/embed/#?secret=dPOYCiCYoq" data-secret="dPOYCiCYoq" width="600" height="338" title="&#8220;PostgreSQL: Script to Kill all Running Connections and Sessions of a Database&#8221; &#8212; Database Research &amp; Development" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe></p>
<p>In this post, I am sharing small, but a very important note on PostgreSQL pg_terminate_backend and pg_cancel_backend which are used to kill the running query or session. </p>
<p><strong>pg_cancel_backend():</strong> </p>
<blockquote><p>It cancels the only running query. You can get the list of long running queries (pid) using pg_stat_activity.</p></blockquote>
<blockquote><p>If you want to kill any of those long running queries, you must use pg_cancel_backend() to kill it. You can cancel one query without destroying the connection, stopping the other queries.</p></blockquote>
<p><strong>pg_terminate_backend():</strong></p>
<blockquote><p>It terminates the entire process and database connection. It destroys everything for that particular role or user. </p></blockquote>
<blockquote><p>If you are very serious about to terminate the session without cancelling it, you can use this function otherwise you should avoid the use of this function.</p></blockquote>
<p><strong>The best practice is:</strong> </p>
<blockquote><p>First find long running queries and their process ids (pid), cancel those queries using pg_cancel_backend and if it is not releasing, you should use pg_terminate_backend.</p></blockquote>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
