Robert Haas <robertmh...@gmail.com> writes: > On Mon, Mar 27, 2017 at 1:48 AM, Rafia Sabih > <rafia.sa...@enterprisedb.com> wrote: >> This is caused because trigger related functions are marked safe and >> using global variables, hence when executed in parallel are giving >> incorrect output.
> If it's just that they are relying on unsynchronized global variables, > then it's sufficient to mark them parallel-restricted ('r'). Do we > really need to go all the way to parallel-unsafe ('u')? Color me confused, but under what circumstances would triggers get executed by a parallel worker at all? I thought we did not allow updating queries to be parallelized. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers