Re: [HACKERS] Optional message to user when terminating/cancelling backend
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@enterprisedb.com>, Andres Freund <andres@anarazel.de>, Onder Kalaci <onder@citusdata.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2018-10-02T00:39:59Z
Lists: pgsql-hackers
On Mon, Oct 01, 2018 at 02:37:42PM +0200, Daniel Gustafsson wrote: >> On 1 Oct 2018, at 01:19, Michael Paquier <michael@paquier.xyz> wrote: >> Looking at the refactoring patch 0001, wouldn't signalfuncs.c make a >> better name for the new file? There are already multiple examples of >> this type, like logicalfuncs.c, slotfuncs.c, etc. > > I have no strong feelings on this, I was merely using the name that Alvaro > suggested when he brought up the refactoring as an extension of this patch. > signalfuncs.c is fine by me, so I did this rename in the attached revision. Indeed, I missed the previous part posted here: https://www.postgresql.org/message-id/20180124154548.gmpyvkzlsijren7u@alvherre.pgsql Alvaro, do you have a strong preference over one or the other? -- 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