pgsql: Improve comment in get_partition_dispatch_recurse.

Improve comment in get_partition_dispatch_recurse. David Rowley, reviewed by Amit Langote, and revised a bit by me. Discussion: http://postgr.es/m/CAKJS1f9yyimYyFzbHM4EwE+tkj4jvrHqSH0H4S4Kbas=ufp...@mail.gmail.com Branch -- master Details ---

pgsql: Pass the correct PlannerInfo to PlanForeignModify/PlanDirectModi

Pass the correct PlannerInfo to PlanForeignModify/PlanDirectModify. Previously, we passed the toplevel PlannerInfo, but we actually want to pass the relevant subroot. One problem with passing the toplevel PlannerInfo is that the FDW which wants to push down an UPDATE or DELETE against a join

pgsql: Fix misprocessing of equivalence classes involving record_eq().

Fix misprocessing of equivalence classes involving record_eq(). canonicalize_ec_expression() is supposed to agree with coerce_type() as to whether a RelabelType should be inserted to make a subexpression be valid input for the operators of a given opclass. However, it did the wrong thing with

pgsql: Fix misprocessing of equivalence classes involving record_eq().

Fix misprocessing of equivalence classes involving record_eq(). canonicalize_ec_expression() is supposed to agree with coerce_type() as to whether a RelabelType should be inserted to make a subexpression be valid input for the operators of a given opclass. However, it did the wrong thing with

pgsql: Fix misprocessing of equivalence classes involving record_eq().

Fix misprocessing of equivalence classes involving record_eq(). canonicalize_ec_expression() is supposed to agree with coerce_type() as to whether a RelabelType should be inserted to make a subexpression be valid input for the operators of a given opclass. However, it did the wrong thing with

pgsql: Fix misprocessing of equivalence classes involving record_eq().

Fix misprocessing of equivalence classes involving record_eq(). canonicalize_ec_expression() is supposed to agree with coerce_type() as to whether a RelabelType should be inserted to make a subexpression be valid input for the operators of a given opclass. However, it did the wrong thing with

pgsql: Fix misprocessing of equivalence classes involving record_eq().

Fix misprocessing of equivalence classes involving record_eq(). canonicalize_ec_expression() is supposed to agree with coerce_type() as to whether a RelabelType should be inserted to make a subexpression be valid input for the operators of a given opclass. However, it did the wrong thing with

pgsql: Fix misprocessing of equivalence classes involving record_eq().

Fix misprocessing of equivalence classes involving record_eq(). canonicalize_ec_expression() is supposed to agree with coerce_type() as to whether a RelabelType should be inserted to make a subexpression be valid input for the operators of a given opclass. However, it did the wrong thing with

pgsql: Detoast plpgsql variables if they might live across a transactio

Detoast plpgsql variables if they might live across a transaction boundary. Up to now, it's been safe for plpgsql to store TOAST pointers in its variables because the ActiveSnapshot for whatever query called the plpgsql function will surely protect such TOAST values from being vacuumed away, even

pgsql: doc: PG 11 release notes adjustments

doc: PG 11 release notes adjustments Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b2b82228ee5dc08f0341b5480546479c19e84baf Modified Files -- doc/src/sgml/release-11.sgml | 21 ++--- 1 file changed, 14 insertions(+), 7 deletions(-)