Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly

Joe Conway <mail@joeconway.com>

From: Joe Conway <mail@joeconway.com>

To: Tom Lane <tgl@sss.pgh.pa.us>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>

Cc: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>, Robert Haas <robertmhaas@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Rushabh Lathia <rushabh.lathia@gmail.com>, Michael Paquier <michael.paquier@gmail.com>

Date: 2018-03-05T20:11:46Z

Lists: pgsql-hackers

On 03/05/2018 11:19 AM, Tom Lane wrote:
> Joe, I wonder if you could add "log_autovacuum_min_duration = 0" to
> rhinoceros' extra_config options, temporarily?  Correlating that log
> output with the log_statement output from the test proper would let
> us confirm or deny whether it's autovacuum.


Done just now. Do you want me to force a run?


Joe

-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development

Commits

Temporarily instrument postgres_fdw test to look for statistics changes.
- c2c537c56dc3 11.0 landed
postgres_fdw: Fourth attempt to stabilize regression tests.
- 1733460f0205 11.0 landed
postgres_fdw: Third attempt to stabilize regression tests.
- 4fa396464e5f 11.0 landed
postgres_fdw: Attmempt to stabilize regression tests.
- 958e20e42d6c 11.0 landed
postgres_fdw: Push down UPDATE/DELETE joins to remote servers.
- 1bc0100d270e 11.0 landed