v17-0003-DO-SELECT-add-info-to-mvcc.sgml.patch
application/octet-stream
Filename: v17-0003-DO-SELECT-add-info-to-mvcc.sgml.patch
Type: application/octet-stream
Part: 2
Message:
Re: ON CONFLICT DO SELECT (take 3)
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch v17-0003
Subject: DO SELECT - add info to mvcc.sgml
| File | + | − |
|---|---|---|
| doc/src/sgml/mvcc.sgml | 10 | 0 |
From 68ce50ef0dd617a32d35c07ca2e59e0605bba725 Mon Sep 17 00:00:00 2001
From: Viktor Holmberg <v@viktorh.net>
Date: Tue, 25 Nov 2025 13:56:16 +0100
Subject: [PATCH v17 3/3] DO SELECT - add info to mvcc.sgml
---
doc/src/sgml/mvcc.sgml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index 049ee75a4ba..f2d5c8ed032 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -366,6 +366,16 @@
conventionally visible to the command.
</para>
+ <para>
+ <command>INSERT</command> with an <literal>ON CONFLICT DO
+ SELECT</literal> clause behaves similarly to <literal>ON CONFLICT DO
+ UPDATE</literal>. In Read Committed mode, if a conflict originates
+ in another transaction whose effects are not yet visible to the
+ <command>INSERT</command>, the <literal>SELECT</literal> clause will
+ return that row, even though possibly <emphasis>no</emphasis> version
+ of that row is conventionally visible to the command.
+ </para>
+
<para>
<command>INSERT</command> with an <literal>ON CONFLICT DO
NOTHING</literal> clause may have insertion not proceed for a row due to
--
2.48.1