Andres Freund <and...@2ndquadrant.com> writes: > I wonder what to do about bgworker's bgworker_die()? I don't really see > how that can be fixed without breaking the API?
IMO it should be flushed and bgworkers should use the same die() handler as every other backend, or else one like the one in worker_spi, which just sets a flag for testing later. If we try to change the signal handling contracts, 80% of backend code will be unusable in bgworkers, which is not where we want to be I think. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers