aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/ruleutils.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2017-03-24 12:00:53 -0400
committerRobert Haas <rhaas@postgresql.org>2017-03-24 12:00:53 -0400
commit857ee8e391ff6654ef9dcc5dd8b658d7709d0a3c (patch)
tree1d0f54ef032aa0a90bcda70e86ee3850167462ad /src/backend/utils/adt/ruleutils.c
parent42b4b0b2413b9b472aaf2112a3bbfd80a6ab4dc5 (diff)
downloadpostgresql-857ee8e391ff6654ef9dcc5dd8b658d7709d0a3c.tar.gz
postgresql-857ee8e391ff6654ef9dcc5dd8b658d7709d0a3c.zip
Add a txid_status function.
If your connection to the database server is lost while a COMMIT is in progress, it may be difficult to figure out whether the COMMIT was successful or not. This function will tell you, provided that you don't wait too long to ask. It may be useful in other situations, too. Craig Ringer, reviewed by Simon Riggs and by me Discussion: http://postgr.es/m/CAMsr+YHQiWNEi0daCTboS40T+V5s_+dst3PYv_8v2wNVH+Xx4g@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/ruleutils.c')
0 files changed, 0 insertions, 0 deletions