diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-01-04 15:11:43 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-01-04 15:11:43 -0500 |
commit | 7debf36072b3a088b3003aab6dcf57c3f186100d (patch) | |
tree | 87e151833f30a3d5a39b2a5bc52d922898f9f466 /src/backend/utils/adt/numeric.c | |
parent | 5d35438273c4523a4dc4b48c3bd575e64310d3d4 (diff) | |
download | postgresql-7debf36072b3a088b3003aab6dcf57c3f186100d.tar.gz postgresql-7debf36072b3a088b3003aab6dcf57c3f186100d.zip |
Docs: provide a concrete discussion and example for RLS race conditions.
Commit 43cd468cf01007f3 added some wording to create_policy.sgml purporting
to warn users against a race condition of the sort that had been noted some
time ago by Peter Geoghegan. However, that warning was far too vague to be
useful (or at least, I completely failed to grasp what it was on about).
Since the problem case occurs with a security design pattern that lots of
people are likely to try to use, we need to be as clear as possible about
it. Provide a concrete example in the main-line docs in place of the
original warning.
Diffstat (limited to 'src/backend/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions