Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly - Mailing list pgsql-hackers

From Robert Haas
Subject Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
Date
Msg-id CA+TgmoZOpGnmss2dpOAktHc30NS=StmLw-ChkJkd74DLo_nyEA@mail.gmail.com
Whole thread Raw
In response to Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
On Fri, Mar 2, 2018 at 1:20 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Mar 2, 2018 at 5:35 AM, Etsuro Fujita
> <fujita.etsuro@lab.ntt.co.jp> wrote:
>> Agreed.  Better safe than sorry, so I disabled autovacuum for all the tables
>> created in the postgres_fdw regression test, except the ones with no data
>> modification created in the sections "test handling of collations" and "test
>> IMPORT FOREIGN SCHEMA".  I'm attaching a patch for that.
>
> I have committed this patch.  Whee!

And that seems to have made things worse.  The failures on rhinocerous
look related:

https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=rhinoceros&br=HEAD

And so does this failure on chub:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chub&dt=2018-03-02%2016%3A10%3A02

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Testing "workers launched" in expected output? Really?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] [FEATURE PATCH] pg_stat_statements with plans (v02)