On Wed, Jun 21, 2017 at 11:42 PM, Daniel Gustafsson <dan...@yesql.se> wrote: > The message is truncated in SetBackendCancelMessage() for safety, but > pg_{cancel|terminate}_backend() could throw an error on too long message, or > warning truncation, to the caller as well. Personally I think a warning is > the > appropriate response, but I don’t really have a strong opinion.
And a NOTICE? That's what happens for relation name truncation. You are right that having a check in SetBackendCancelMessage() makes the most sense as bgworkers could just call the low level API. Isn't the concept actually closer to just a backend message? This slot could be used for other purposes than cancellation. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers