pgsql: Fix invalid value of synchronous_commit in description of flush_

Fix invalid value of synchronous_commit in description of flush_lag "remote_flush" has never been a valid user-facing value, but "on" is. Author: Maksim Milyutin Discussion: https://postgr.es/m/27b3b80c-3615-2d76-02c5-44566b531...@gmail.com Branch -- REL_10_STABLE Details --- https://gi

pgsql: Fix invalid value of synchronous_commit in description of flush_

Fix invalid value of synchronous_commit in description of flush_lag "remote_flush" has never been a valid user-facing value, but "on" is. Author: Maksim Milyutin Discussion: https://postgr.es/m/27b3b80c-3615-2d76-02c5-44566b531...@gmail.com Branch -- master Details --- https://git.postg

pgsql: Fix invalid value of synchronous_commit in description of flush_

Fix invalid value of synchronous_commit in description of flush_lag "remote_flush" has never been a valid user-facing value, but "on" is. Author: Maksim Milyutin Discussion: https://postgr.es/m/27b3b80c-3615-2d76-02c5-44566b531...@gmail.com Branch -- REL_11_STABLE Details --- https://gi

pgsql: Fix typo

Fix typo Backends don't typically exist uncleanly, but they can certainly exit uncleanly, and it's exiting uncleanly that's being discussed here. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f502fc88b3c8b4c619a4bcbb86c3225a699c1d45 Modified Files --

pgsql: postgres_fdw: Improve cost and size estimation for aggregate pus

postgres_fdw: Improve cost and size estimation for aggregate pushdown. In commit 7012b132d07c2b4ea15b0b3cb1ea9f3278801d98, which added aggregate pushdown to postgres_fdw, we didn't account for the evaluation cost and the selectivity of HAVING quals attached to ForeignPaths performing aggregate pus