pgsql: Handle table_complete_speculative's succeeded argument as docume

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Handle table_complete_speculative's succeeded argument as docume
Date: 2019-05-14 19:21:38
Message-ID: E1hQcza-0000Lk-4m@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Handle table_complete_speculative's succeeded argument as documented.

For some reason both callsite and the implementation for heapam had
the meaning inverted (i.e. succeeded == true was passed in case of
conflict). That's confusing.

I (Andres) briefly pondered whether it'd be better to rename
table_complete_speculative's argument to 'bool specConflict' or such,
but decided not to. The 'complete' in the function name for me makes
`succeeded` sound a bit better.

Reported-By: Ashwin Agrawal, Melanie Plageman, Heikki Linnakangas
Discussion:
https://postgr.es/m/CALfoeitk7-TACwYv3hCw45FNPjkA86RfXg4iQ5kAOPhR+F1Y4w@mail.gmail.com
https://postgr.es/m/97673451-339f-b21e-a781-998d06b1067c@iki.fi

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/aa4b8c61d2cd57b53be03defb04d59b232a0e150

Modified Files
--------------
src/backend/access/heap/heapam_handler.c | 2 +-
src/backend/executor/nodeModifyTable.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2019-05-15 00:01:07 Re: pgsql: Compute XID horizon for page level index vacuum on primary.
Previous Message Andres Freund 2019-05-14 19:06:44 pgsql: Add isolation test for INSERT ON CONFLICT speculative insertion