Skip site navigation (1) Skip section navigation (2)

Hot Standby and cancelling idle queries

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Hot Standby and cancelling idle queries
Date: 2009-11-25 14:00:38
Message-ID: 1259157638.27757.11336.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-hackers
Recent change:

An idle-in-transaction transaction can also hold a temporary file. Think
of an open cursor, for example. Therefore, remove the distinction
between CONFLICT_MODE_ERROR and CONFLICT_MODE_ERROR_IF_NOT_IDLE,
idle-in-transaction backends need to be killed too when a tablespace is
dropped.


Open cursors still have snapshots, so they would not be treated as idle
in transaction. If the user has a held cursor then they can keep it,
since it has already read the database and released the snapshot. So
this change seems both unnecessary and harsh, since even if it is
necessary we can work out how to avoid this easily enough.

-- 
 Simon Riggs           www.2ndQuadrant.com


Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2009-11-25 14:02:05
Subject: Re: operator exclusion constraints
Previous:From: Emmanuel CecchetDate: 2009-11-25 13:39:27
Subject: Re: Partitioning option for COPY

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group