pgsql: Fix comment in be-secure-openssl.c

Fix comment in be-secure-openssl.c Since 573bd08, hardcoded DH parameters have been moved to a different file, making the comment on top of load_dh_buffer() incorrect. Author: Daniel Gustafsson Discussion: https://postgr.es/m/[email protected] Branch -- master De

pgsql: Fix instance of elog() called while holding a spinlock

Fix instance of elog() called while holding a spinlock This broke the project rule to not call any complex code while a spinlock is held. Issue introduced by b89e151. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -

pgsql: Fix instance of elog() called while holding a spinlock

Fix instance of elog() called while holding a spinlock This broke the project rule to not call any complex code while a spinlock is held. Issue introduced by b89e151. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -

pgsql: Fix instance of elog() called while holding a spinlock

Fix instance of elog() called while holding a spinlock This broke the project rule to not call any complex code while a spinlock is held. Issue introduced by b89e151. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -

pgsql: Fix instance of elog() called while holding a spinlock

Fix instance of elog() called while holding a spinlock This broke the project rule to not call any complex code while a spinlock is held. Issue introduced by b89e151. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -

pgsql: Fix instance of elog() called while holding a spinlock

Fix instance of elog() called while holding a spinlock This broke the project rule to not call any complex code while a spinlock is held. Issue introduced by b89e151. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -

pgsql: Fix instance of elog() called while holding a spinlock

Fix instance of elog() called while holding a spinlock This broke the project rule to not call any complex code while a spinlock is held. Issue introduced by b89e151. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -

pgsql: Don't call palloc() while holding a spinlock, either.

Don't call palloc() while holding a spinlock, either. Fix some more violations of the "only straight-line code inside a spinlock" rule. These are hazardous not only because they risk holding the lock for an excessively long time, but because it's possible for palloc to throw elog(ERROR), leaving

pgsql: Don't call palloc() while holding a spinlock, either.

Don't call palloc() while holding a spinlock, either. Fix some more violations of the "only straight-line code inside a spinlock" rule. These are hazardous not only because they risk holding the lock for an excessively long time, but because it's possible for palloc to throw elog(ERROR), leaving

pgsql: Don't call palloc() while holding a spinlock, either.

Don't call palloc() while holding a spinlock, either. Fix some more violations of the "only straight-line code inside a spinlock" rule. These are hazardous not only because they risk holding the lock for an excessively long time, but because it's possible for palloc to throw elog(ERROR), leaving

pgsql: Don't call palloc() while holding a spinlock, either.

Don't call palloc() while holding a spinlock, either. Fix some more violations of the "only straight-line code inside a spinlock" rule. These are hazardous not only because they risk holding the lock for an excessively long time, but because it's possible for palloc to throw elog(ERROR), leaving