Re: [POC] hash partitioning

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: amul sul <sulamul@gmail.com>

Cc: Dilip Kumar <dilipbalaut@gmail.com>, Yugo Nagata <nagata@sraoss.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, David Steele <david@pgmasters.net>, Greg Stark <stark@mit.edu>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2017-09-08T01:15:44Z

Lists: pgsql-hackers

On Mon, Sep 4, 2017 at 6:38 AM, amul sul <sulamul@gmail.com> wrote:
> I've updated patch to use an extended hash function (Commit #
> 81c5e46c490e2426db243eada186995da5bb0ba7) for the partitioning.

Committed 0001 after noticing that Jeevan Ladhe also found that change
convenient for default partitioning.  I made a few minor cleanups;
hopefully I didn't break anything.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL 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