> On 26 Jan 2018, at 00:05, Daniel Gustafsson <dan...@yesql.se> wrote: > >> On 24 Jan 2018, at 16:45, Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote:
>> Maybe have two patches, 0001 creates the files moving the contents over, >> then 0002 adds your new stuff on top. > > The two attached patches implements this. Attached are rebased patches to cope with the recent pgproc changes. I also made the function cope with NULL messages, not because it’s a sensible value but I can see this function being fed from a sub-SELECT which could return NULL. As per the previous mail, 0001 refactors the signal code according to Alvaros suggestion and 0002 implements $subject on top of the refactoring. cheers ./daniel
0001-Refactor-backend-signalling-code-v7.patch
Description: Binary data
0002-Support-optional-message-in-backend-cancel-terminate-v7.patch
Description: Binary data
