Re: [POC] hash partitioning
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
From: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: amul sul <sulamul@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-05-16T03:45:43Z
Lists: pgsql-hackers
On Mon, May 15, 2017 at 9:13 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Mon, May 15, 2017 at 6:57 AM, amul sul <sulamul@gmail.com> wrote: >>> Collation is only relevant for ordering, not equality. Since hash >>> opclasses provide only equality, not ordering, it's not relevant here. >>> I'm not sure whether we should error out if it's specified or just >>> silently ignore it. Maybe an ERROR is a good idea? But not sure. >>> >> IMHO, we could simply have a WARNING, and ignore collation, thoughts? >> >> Updated patches attached. > > I think that WARNING is rarely a good compromise between ERROR and > nothing. I think we should just decide whether this is legal (and > then allow it without a WARNING) or not legal (and then ERROR). > Telling the user that it's allowed but we don't like it doesn't really > help much. +1. We should throw an error and add a line in documentation that collation should not be specified for hash partitioned table. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
Refactor get_partition_for_tuple a bit.
- f0a0c17c1b12 11.0 landed
-
Adopt Bob Jenkins' improved hash function for hash_any(). This changes the
- 8205258fa675 8.4.0 cited
-
Improve hash_any() to use word-wide fetches when hashing suitably aligned
- 2604359251d3 8.4.0 cited