Re: [HACKERS] Optional message to user when terminating/cancelling backend
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, Andres Freund <andres@anarazel.de>, Onder Kalaci <onder@citusdata.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2018-07-06T01:47:05Z
Lists: pgsql-hackers
On Fri, Jul 06, 2018 at 12:18:02PM +1200, Thomas Munro wrote: > 6118 --select pg_cancel_backend(pg_backend_pid(), 'it brings on many changes'); > 6119 select pg_cancel_backend(pg_backend_pid(), NULL); > 6120! ERROR: canceling statement due to user request > 6121--- 25,32 ---- > 6122 > 6123 --select pg_cancel_backend(pg_backend_pid(), 'it brings on many changes'); > 6124 select pg_cancel_backend(pg_backend_pid(), NULL); > 6125! pg_cancel_backend > 6126! ------------------- > 6127! t > > Apparently Windows can take or leave it as it pleases. > > https://ci.appveyor.com/project/postgresql-cfbot/postgresql/build/1.0.4488 The test coverage looks adapted if it is possible to catch such failures, so that's nice. +select pg_cancel_backend(); +ERROR: function pg_cancel_backend() does not exist +LINE 1: select pg_cancel_backend(); This negative test is not really necessary. -- Michael
Commits
-
Refactor user-facing SQL functions signalling backends
- 09921f397b84 12.0 landed
-
Introduce 64-bit hash functions with a 64-bit seed.
- 81c5e46c490e 11.0 cited