pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Cc: Rushabh Lathia <rushabh.lathia@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Subject: Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
Date: Mon, 05 Mar 2018 12:21:29 +0900
Message-ID: <5A9CB7B9.2040008@lab.ntt.co.jp> (raw )
In-Reply-To: <CA+TgmoZOpGnmss2dpOAktHc30NS=StmLw-ChkJkd74DLo_nyEA@mail.gmail.com >
References: <5A438A45.2000909@lab.ntt.co.jp >
<5A57193A.2080003@lab.ntt.co.jp >
<CA+TgmoYef9czAA1gJeqh4v47Tv=dqOp4EfdU6bV8EYkOdCwvUw@mail.gmail.com >
<6166.1518044513@sss.pgh.pa.us >
<CA+TgmoaxGGZyUAWQMz7c-3V85TV5-w2wmvpOYrLnALi2d9Z-dQ@mail.gmail.com >
<5A7BE8E6.200@lab.ntt.co.jp >
<28606.1518105934@sss.pgh.pa.us >
<CA+Tgmobf+AXEwO4r0oCkvNhkaVnxPgoJaApoX+rAi0G7-N-Dyg@mail.gmail.com >
<5A7CFDDA.8050906@lab.ntt.co.jp >
<5A7D76CF.8080601@lab.ntt.co.jp >
<CA+TgmoaAQCn0+xh3JG2avn35Lukj2NVmhxVi7hE2CwzSUQ-5ag@mail.gmail.com >
<20134.1518201188@sss.pgh.pa.us >
<CA+TgmoY5KNf-Y=zOdHVfa8Lmo=OMJe=dBpP-noT_1fdVK6EYPA@mail.gmail.com >
<18653.1518297871@sss.pgh.pa.us >
<5A82DCCE.3060107@lab.ntt.co.jp >
<29147.1519769644@sss.pgh.pa.us >
<CA+Tgmob_WGK+vKzE6FmrMmuwuv4myntfRAkEbo+tsDt9xUwCLQ@mail.gmail.com >
<23783.1519929258@sss.pgh.pa.us >
<5A9928F1.2010206@lab.ntt.co.jp >
<CA+TgmoaNWpQ+F7_DtiJpc62PUJ6JQBAQpT1H7CBrjKmryGGgkw@mail.gmail.com >
<CA+TgmoZOpGnmss2dpOAktHc30NS=StmLw-ChkJkd74DLo_nyEA@mail.gmail.com >
(2018/03/03 5:01), Robert Haas wrote:
> 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!
Thank you for taking the time on this!
> 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
Totally outdated stats used in query planning causes the failures?
ANALYZE right before the plan-changing queries would fix the failures?
> 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
The Git log shows that this was done before the commit.
Best regards,
Etsuro Fujita
view thread (33+ messages) latest in thread
Message-ID: <5A9CB7B9.2040008@lab.ntt.co.jp>
Permalink: ../5A9CB7B9.2040008@lab.ntt.co.jp/
Also on: postgresql.org/message-id/5A9CB7B9.2040008@lab.ntt.co.jp
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: fujita.etsuro@lab.ntt.co.jp, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, rushabh.lathia@gmail.com, michael.paquier@gmail.com, ashutosh.bapat@enterprisedb.com
Subject: Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
In-Reply-To: <5A9CB7B9.2040008@lab.ntt.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox