postgresql/contrib/vacuumlo
Heikki Linnakangas 77b68e3a4f Fix copy-pasto in freeing memory on error in vacuumlo.
It's harmless to call PQfreemem() with a NULL argument, so the only
consequence was that if allocating 'schema' failed, but allocating 'table'
or 'field' succeeded, we would leak a bit of memory. That's highly
unlikely to happen, so this is just academical, but let's get it right.

Per bug #15838 from Timur Birsh. Backpatch back to 9.5, where the
PQfreemem() calls were introduced.

Discussion: https://www.postgresql.org/message-id/15838-3221652c72c5e69d@postgresql.org
2019-06-07 12:42:27 +03:00
..
t Rework option set of vacuumlo 2018-08-28 21:42:45 +09:00
.gitignore Rework option set of vacuumlo 2018-08-28 21:42:45 +09:00
Makefile Add PGXS options to control TAP and isolation tests, take two 2018-12-03 09:27:35 +09:00
vacuumlo.c Fix copy-pasto in freeing memory on error in vacuumlo. 2019-06-07 12:42:27 +03:00