pgsql: Ensure that contrib/pgstattuple functions respond to cancel

Started by Tom Laneabout 16 years ago3 messageshackers
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

Log Message:
-----------
Ensure that contrib/pgstattuple functions respond to cancel interrupts
reasonably promptly, by adding CHECK_FOR_INTERRUPTS in the per-page loops.

Tatsuhito Kasahara

Tags:
----
REL7_4_STABLE

Modified Files:
--------------
pgsql/contrib/pgstattuple:
pgstattuple.c (r1.12.4.2 -> r1.12.4.3)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pgstattuple/pgstattuple.c?r1=1.12.4.2&r2=1.12.4.3)

#2Robert Haas
robertmhaas@gmail.com
In reply to: Tom Lane (#1)
Re: [COMMITTERS] pgsql: Ensure that contrib/pgstattuple functions respond to cancel

On Fri, Apr 2, 2010 at 12:17 PM, Tom Lane <tgl@postgresql.org> wrote:

Log Message:
-----------
Ensure that contrib/pgstattuple functions respond to cancel interrupts
reasonably promptly, by adding CHECK_FOR_INTERRUPTS in the per-page loops.

Tatsuhito Kasahara

This patch seems to have overlooked pgstatindex().

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

#3Robert Haas
robertmhaas@gmail.com
In reply to: Robert Haas (#2)
Re: [COMMITTERS] pgsql: Ensure that contrib/pgstattuple functions respond to cancel

On Wed, Aug 31, 2011 at 4:24 PM, Robert Haas <robertmhaas@gmail.com> wrote:

On Fri, Apr 2, 2010 at 12:17 PM, Tom Lane <tgl@postgresql.org> wrote:

Log Message:
-----------
Ensure that contrib/pgstattuple functions respond to cancel interrupts
reasonably promptly, by adding CHECK_FOR_INTERRUPTS in the per-page loops.

Tatsuhito Kasahara

This patch seems to have overlooked pgstatindex().

Fixed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company