Your message dated Mon, 8 Aug 2016 16:05:12 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-postgresql-public] Bug#255208: obsolete?
has caused the Debian Bug report #255208,
regarding postgresql - ignores SIGPIPE
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
255208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255208
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql
Version: 7.4.3-1
Severity: important
The postgres daemon ignores SIGPIPE. This makes it impossible to cancel
queries if the client is not able to issue a cancel command, like the
perl and python bindings.
The code contains a signal handler for SIGINT which cancels the actual
query, so I see no problem to have SIGPIPE behave the same way.
Bastian
--
You're dead, Jim.
-- McCoy, "The Tholian Web", stardate unknown
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Re: Peter Eisentraut 2016-08-08
<[email protected]>
> Since PostgreSQL 9.2, an unprivileged user can cancel their own queries
> using pg_cancel_backend(). So I think the original reason behind this
> complaint is obsolete. I propose to close this bug.
Agreed.
I'm still curious why PG doesn't just cancel the query by itself on
SIGPIPE. Is there any value in running queries to completion when the
user has already left? Are these queries even committed?
Christoph
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-postgresql-public mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
