mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: mention of postpostgres_fdw INSERT ON CONFLICT limitation

Browse Source 
Reported-by: Fujii Masao

Discussion: https://postgr.es/m/47801526-d017-4c89-9f52-c02c449a139b@oss.nttdata.com

Author: Fujii Masao

Backpatch-through: master
This commit is contained in:
Bruce Momjian 2024-08-19 19:54:39 -04:00
parent cf3bb26204
commit e28a2719be
1 changed files with 11 additions and 1 deletions

12
doc/src/sgml/postgres-fdw.sgml

@ -1096,7 +1096,10 @@ postgres=# SELECT postgres_fdw_disconnect_all();
<para>
<filename>postgres_fdw</filename> can be used with remote servers dating back
to <productname>PostgreSQL</productname> 8.3. Read-only capability is available
back to 8.1. A limitation however is that <filename>postgres_fdw</filename>
back to 8.1.
</para>
<para>
A limitation however is that <filename>postgres_fdw</filename>
generally assumes that immutable built-in functions and operators are
safe to send to the remote server for execution, if they appear in a
<literal>WHERE</literal> clause for a foreign table. Thus, a built-in
@ -1108,6 +1111,13 @@ postgres=# SELECT postgres_fdw_disconnect_all();
optimization fence, and placing the problematic function or operator
outside the sub-<literal>SELECT</literal>.
</para>
<para>
Another limitation is that when executing <command>INSERT</command>
statements with an <literal>ON CONFLICT DO NOTHING</literal> clause on
a foreign table, the remote server must be running
<productname>PostgreSQL</productname> 9.5 or later,
as earlier versions do not support this feature.
</para>
</sect2>
<sect2 id="postgres-fdw-wait-events">