pgsql: Doc: note that statement-level view triggers require an INSTEAD

2018-03-18 Thread Tom Lane
Doc: note that statement-level view triggers require an INSTEAD OF trigger. If a view lacks an INSTEAD OF trigger, DML on it can only work by rewriting the command into a command on the underlying base table(s). Then we will fire triggers attached to those table(s), not those for the view. This

pgsql: Doc: note that statement-level view triggers require an INSTEAD

2018-03-18 Thread Tom Lane
Doc: note that statement-level view triggers require an INSTEAD OF trigger. If a view lacks an INSTEAD OF trigger, DML on it can only work by rewriting the command into a command on the underlying base table(s). Then we will fire triggers attached to those table(s), not those for the view. This

pgsql: Doc: note that statement-level view triggers require an INSTEAD

2018-03-18 Thread Tom Lane
Doc: note that statement-level view triggers require an INSTEAD OF trigger. If a view lacks an INSTEAD OF trigger, DML on it can only work by rewriting the command into a command on the underlying base table(s). Then we will fire triggers attached to those table(s), not those for the view. This

pgsql: Doc: note that statement-level view triggers require an INSTEAD

2018-03-18 Thread Tom Lane
Doc: note that statement-level view triggers require an INSTEAD OF trigger. If a view lacks an INSTEAD OF trigger, DML on it can only work by rewriting the command into a command on the underlying base table(s). Then we will fire triggers attached to those table(s), not those for the view. This

pgsql: Doc: note that statement-level view triggers require an INSTEAD

2018-03-18 Thread Tom Lane
Doc: note that statement-level view triggers require an INSTEAD OF trigger. If a view lacks an INSTEAD OF trigger, DML on it can only work by rewriting the command into a command on the underlying base table(s). Then we will fire triggers attached to those table(s), not those for the view. This

pgsql: Doc: note that statement-level view triggers require an INSTEAD

2018-03-18 Thread Tom Lane
Doc: note that statement-level view triggers require an INSTEAD OF trigger. If a view lacks an INSTEAD OF trigger, DML on it can only work by rewriting the command into a command on the underlying base table(s). Then we will fire triggers attached to those table(s), not those for the view. This

pgsql: Fix pg_recvlogical for pre-10 versions

2018-03-18 Thread Magnus Hagander
Fix pg_recvlogical for pre-10 versions In e170b8c8, protection against modified search_path was added. However, PostgreSQL versions prior to 10 does not accept SQL commands over a replication connection, so the protection would generate a syntax error. Since we cannot run SQL commands on it, we a

pgsql: Fix pg_recvlogical for pre-10 versions

2018-03-18 Thread Magnus Hagander
Fix pg_recvlogical for pre-10 versions In e170b8c8, protection against modified search_path was added. However, PostgreSQL versions prior to 10 does not accept SQL commands over a replication connection, so the protection would generate a syntax error. Since we cannot run SQL commands on it, we a

pgsql: Fix pg_recvlogical for pre-10 versions

2018-03-18 Thread Magnus Hagander
Fix pg_recvlogical for pre-10 versions In e170b8c8, protection against modified search_path was added. However, PostgreSQL versions prior to 10 does not accept SQL commands over a replication connection, so the protection would generate a syntax error. Since we cannot run SQL commands on it, we a

pgsql: Fix pg_recvlogical for pre-10 versions

2018-03-18 Thread Magnus Hagander
Fix pg_recvlogical for pre-10 versions In e170b8c8, protection against modified search_path was added. However, PostgreSQL versions prior to 10 does not accept SQL commands over a replication connection, so the protection would generate a syntax error. Since we cannot run SQL commands on it, we a

pgsql: Fix pg_recvlogical for pre-10 versions

2018-03-18 Thread Magnus Hagander
Fix pg_recvlogical for pre-10 versions In e170b8c8, protection against modified search_path was added. However, PostgreSQL versions prior to 10 does not accept SQL commands over a replication connection, so the protection would generate a syntax error. Since we cannot run SQL commands on it, we a