aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/basics.source
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2017-04-20 23:12:57 +0900
committerFujii Masao <fujii@postgresql.org>2017-04-20 23:12:57 +0900
commit8bbc618b4825b13a9776f2289acd06483e140300 (patch)
tree1765ae9ba5a7b00a8f593f50473a4920f467302a /src/tutorial/basics.source
parente68432a0e1ad07b6848fc9bbc11e382eb43b8618 (diff)
downloadpostgresql-8bbc618b4825b13a9776f2289acd06483e140300.tar.gz
postgresql-8bbc618b4825b13a9776f2289acd06483e140300.zip
Don't call the function that may raise an error while holding spinlock.
It's not safe to raise an error while holding spinlock. But previously logical replication worker for table sync called the function which reads the system catalog and may raise an error while it's holding spinlock. Which could lead to the trouble where spinlock will never be released and the server gets stuck infinitely. Author: Petr Jelinek Reviewed-by: Kyotaro Horiguchi and Fujii Masao Reported-by: Fujii Masao Discussion: http://postgr.es/m/CAHGQGwFDWh_Qr-q_GEMpD+qH=vYPMdVqw=ZOSY3kX_Pna9R9SA@mail.gmail.com
Diffstat (limited to 'src/tutorial/basics.source')
0 files changed, 0 insertions, 0 deletions