Fix possible leak of semaphore count. Commit 4aec49899e5782247e134f94ce1c6ee926f88e1c reorganized the order of operations here so that we no longer increment the number of "extra waits" before locking the semaphore, but it did not change the starting value of extraWaits from 0 to -1 to compensate. In the worst case, this could leak a semaphore count, but that seems to be unlikely in practice.
Discussion: http://postgr.es/m/caa4ek1jyvqximba+-a589rk0pyhsykkgxeumvkju6y74hdr...@mail.gmail.com Amit Kapila, per an off-list report by Dilip Kumar. Reviewed by me. Branch ------ REL9_6_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/603299167f4aaa857c0156b492ad51143e33fc2f Modified Files -------------- src/backend/storage/ipc/procarray.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
