postgres

History

Tom Lane 601084eb1a Fix unsafe memory management in CloneRowTriggersToPartition().

It's not really supported to call systable_getnext() in a different
memory context than systable_beginscan() was called in, and it's
*definitely* not safe to do so and then reset that context between
calls.  I'm not very clear on how this code survived
CLOBBER_CACHE_ALWAYS testing ... but Alexander Lakhin found a case
that would crash it pretty reliably.

Per bug #15828.  Fix, and backpatch to v11 where this code came in.

Discussion: https://postgr.es/m/15828-f6ddd7df4852f473@postgresql.org

2019-06-03 16:59:16 -04:00

backend

Fix unsafe memory management in CloneRowTriggersToPartition().

2019-06-03 16:59:16 -04:00

bin

In the pg_upgrade test suite, don't write to src/test/regress.

2019-05-28 12:59:36 -07:00

common

Tolerate EINVAL when calling fsync() on a directory.

2019-02-24 23:51:54 +13:00

fe_utils

Fix translation of special characters in psql's LaTeX output modes.