summaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeUnique.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2015-07-30 15:19:49 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2015-07-30 15:19:49 -0300
commit71b66e78e432d99325db6356f056cb3f03b3d7b7 (patch)
tree75d8bf5bdc2f005c13adf7b7af70797ed59beaf1 /src/backend/executor/nodeUnique.c
parent244c378e243e3649efc99fe96ec9f123bbe9ffbc (diff)
Fix volatility marking of commit timestamp functions
They are marked stable, but since they act on instantaneous state and it is possible to consult state of transactions as they commit, the results could change mid-query. They need to be marked volatile, and this commit does so. There would normally be a catversion bump here, but this is so much a niche feature and I don't believe there's real damage from the incorrect marking, that I refrained. Backpatch to 9.5, where commit timestamps where introduced. Per note from Fujii Masao.
Diffstat (limited to 'src/backend/executor/nodeUnique.c')
0 files changed, 0 insertions, 0 deletions