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:47:56Z
Lists: pgsql-hackers 
Seems I misremembered the whole opfuncid getting reset thing (it applies
to reading a node from string, not copying) and it was undone by
9f1255ac8593 anyway.  I don't think it makes much of a difference, but I
mention this in case you're wondering why I changed the fix_opfuncids()
call.

-- 
Á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