Re: pgsql: Get rid of copy_partition_key

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Get rid of copy_partition_key
Date: 2017-12-22 16:24:19
Message-ID: 20171222162419.7hocebnsb4fc4yrj@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

Attachment Content-Type Size
0001-Protect-against-hypothetical-memory-leaks-in-Relatio.patch text/plain 4.2 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2017-12-22 16:47:56 Re: pgsql: Get rid of copy_partition_key
Previous Message Tom Lane 2017-12-22 16:00:54 Re: pgsql: Use new overflow aware integer operations.

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-12-22 16:47:56 Re: pgsql: Get rid of copy_partition_key
Previous Message Antonin Houska 2017-12-22 15:43:57 Re: [HACKERS] WIP: Aggregation push-down