Re: [POC] hash partitioning

Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>

From: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>

To: amul sul <sulamul@gmail.com>

Cc: Jesper Pedersen <jesper.pedersen@redhat.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Thom Brown <thom@linux.com>, Robert Haas <robertmhaas@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Yugo Nagata <nagata@sraoss.co.jp>, David Steele <david@pgmasters.net>, Greg Stark <stark@mit.edu>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2017-10-16T09:44:05Z

Lists: pgsql-hackers

On Mon, Oct 16, 2017 at 2:36 PM, Ashutosh Bapat
<ashutosh.bapat@enterprisedb.com> wrote:

>
> Probably we should move changes to partition_bounds_copy() in 0003 to
> 0001, whose name suggests so.
>

We can't do this, hash partition strategy is introduced by 0002. Sorry
for the noise.

-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company

Commits

Add hash partitioning.
- 1aba8e651ac3 11.0 landed
Add sanity check for pg_proc.provariadic
- 35f059e9bdfb 11.0 landed
Add hash_combine64.
- b7f3eb31405f 11.0 landed
Make RelationGetPartitionDispatchInfo expand depth-first.
- 77b6b5e9ceca 11.0 cited
Introduce 64-bit hash functions with a 64-bit seed.
- 81c5e46c490e 11.0 cited
pg_dump: Add a --load-via-partition-root option.
- 23d7680d04b9 11.0 cited