Horton

Re: pgsql: Get rid of copy_partition_key

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Robert Haas <robertmhaas@gmail.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-12-22T16:24:19Z
Lists: pgsql-hackers

Attachments

I believe this patch (which also fixes a comment I neglected to fix in
the previous one) should satisfy your concerns.

It's still running a few relevant tests (create_function_1 create_type
point polygon circle create_table copy create_misc create_index
alter_table partition_join partition_prune hash_part) under
CLOBBER_FREED_MEMORY + CLOBBER_CACHE_ALWAYS, but so far it's looking
good.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Protect against hypothetical memory leaks in RelationGetPartitionKey

  2. Get rid of copy_partition_key