Re: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.
Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
From: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Michael Paquier <michael@paquier.xyz>,
Robert Haas <robertmhaas@gmail.com>,
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>,
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>,
Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-08-29T09:40:03Z
Lists: pgsql-hackers
(2018/08/29 0:21), Jonathan S. Katz wrote: >> On Aug 24, 2018, at 8:38 AM, Etsuro Fujita<fujita.etsuro@lab.ntt.co.jp> wrote: >> (2018/08/24 11:47), Michael Paquier wrote: >>> On Thu, Aug 23, 2018 at 10:00:49PM +0900, Etsuro Fujita wrote: >>>> I tried this today, but doing git behind the corporate firewall doesn't >>>> work. I don't know the clear cause of that, so I'll investigate that >>>> tomorrow. >>> >>> You may be able to tweak that by using https as origin point or proper >>> git proxy settings? >> >> Yeah, my proxy settings were not correct. With the help of my colleagues Horiguchi-san and Yamada-san, I corrected them but still can't clone the master repository. Running git with GIT_CURL_VERBOSE shows that there is another issue in my terminal environment, so I'm trying to resolve that. > > Are there any updates on getting this patch committed? That investigation has shown that the cause is my company firewall, not my terminal environment; that firewall has to be configured to allow me to access to that repository. So, I'm asking my company about that. Best regards, Etsuro Fujita
Commits
-
Adjust EXPLAIN's output for disabled nodes
- 161320b4b960 18.0 cited
-
Disable support for partitionwise joins in problematic cases.
- 940487956ede 11.0 landed
- 7cfdc77023ad 12.0 landed
-
Rewrite the code that applies scan/join targets to paths.
- 11cf92f6e2e1 11.0 cited