pgsql: Re-allow FDWs and custom scan providers to replace joins with ps

2023-08-15 Thread Etsuro Fujita
Re-allow FDWs and custom scan providers to replace joins with pseudoconstant quals. This was disabled in commit 6f80a8d9c due to the lack of support for handling of pseudoconstant quals assigned to replaced joins in createplan.c. To re-allow it, this patch adds the support by 1) modifying the Fo

pgsql: Fix code indentation vioaltion introduced in commit 9e9931d2b.

2023-08-15 Thread Etsuro Fujita
Fix code indentation vioaltion introduced in commit 9e9931d2b. Per buildfarm member koel Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/89be0b89ae60c63856fd26d82a104781540e2312 Modified Files -- contrib/postgres_fdw/postgres_fdw.c | 11 +++ 1 fi

Re: pgsql: Re-allow FDWs and custom scan providers to replace joins with ps

2023-08-15 Thread Etsuro Fujita
I CCed Andrew. On Tue, Aug 15, 2023 at 4:50 PM Etsuro Fujita wrote: > Re-allow FDWs and custom scan providers to replace joins with pseudoconstant > quals. This broke blackhole_fdw, which is tested in buildfarm member crake, because it changed the argument list for create_foreignscan_path(), as

pgsql: doc: PG 16 relnotes, update "current as of" date

2023-08-15 Thread Bruce Momjian
doc: PG 16 relnotes, update "current as of" date Backpatch-through: 16 only Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c5c8bd29b9a22a05f81857c6921c0bc615140cc5 Modified Files -- doc/src/sgml/release-16.sgml | 2 +- 1 file changed, 1 insertio