Re: path toward faster partition pruning
Beena Emerson <memissemerson@gmail.com>
Hello, On Wed, Oct 25, 2017 at 1:07 PM, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote: > On 2017/10/25 15:47, Amit Langote wrote: >> On 2017/10/24 1:38, Beena Emerson wrote: >>> I had noticed this and also that this crash: >>> >>> tprt PARTITION BY RANGE(Col1) >>> tprt_1 FOR VALUES FROM (1) TO (50001) PARTITION BY RANGE(Col1) >>> tprt_11 FOR VALUES FROM (1) TO (10000), >>> tprt_1d DEFAULT >>> tprt_2 FOR VALUES FROM (50001) TO (100001) >>> >>> EXPLAIN (COSTS OFF) SELECT * FROM tprt WHERE col1 BETWEEN 20000 AND 70000; >>> server closed the connection unexpectedly >>> This probably means the server terminated abnormally >>> before or while processing the request. >>> The connection to the server was lost. Attempting reset: Failed. >>> !> >> >> ...and this (crash) were due to bugs in the 0005 patch. > > [ .... ] > >> Should be fixed in the attached updated version. > > Oops, not quite. The crash that Beena reported wasn't fixed (or rather > reintroduced by some unrelated change after once confirming it was fixed). > > Really fixed this time. Some minor comments: 1. wrong function name (0003) The comment on function get_partitions_from_clauses_guts uses wrong name: instead of "_from_", "_using_" is written. /* + * get_partitions_using_clauses_guts + * Determine relation's partitions that satisfy *all* of the clauses + * in the list (return value describes the set of such partitions) + * 2. typo information (0003) +/* + * classify_partition_bounding_keys + * Classify partition clauses into equal, min, max keys, along with any + * Nullness constraints and return that informatin in the output argument 3. misspell admissible (0003) + * columns, whereas a prefix of all partition key columns is addmissible + * as min and max keys. 4. double and? (0002) + * as part of the operator family, check if its negator + * exists and and that the latter is compatible with 5. typo inequality (0002) + * (key < val OR key > val), if the partitioning method + * supports such notion of inequlity. 6. typo output (0005) + * return it as the only scannable partition, that means the query + * doesn't want null values in its outout. 7. typo provide (0005) + /* Valid keys->eqkeys must provoide all partition keys. */ + Assert(keys->n_eqkeys == 0 || keys->n_eqkeys == partkey->partnatts); 8. comment of struct PartClause (0003) +/* + * Information about a clause matched with a partition key column kept to + * avoid repeated recomputation in remove_redundant_clauses(). + */ Instead of repeated recomputation, we can use just " repeated computation" or just " recomputation" -- Beena Emerson EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Fix assorted partition pruning bugs
- d758d9702e2f 11.0 landed
-
Make gen_partprune_steps static
- d1e2cac5ff7e 11.0 landed
-
Remove useless 'default' clause
- c775fb9e18ac 11.0 landed
-
Reorganize partitioning code
- da6f3e45ddb6 11.0 landed
-
Use custom hash opclass for hash partition pruning
- fafec4cce814 11.0 landed
-
Blindly attempt to fix sepgsql tests broken due to 9fdb675fc5.
- 4f813c7203e0 11.0 landed
-
Attempt to fix endianess issues in new hash partition test.
- 40e42e1024c5 11.0 landed
-
Faster partition pruning
- 9fdb675fc5d2 11.0 landed
-
For partitionwise join, match on partcollation, not parttypcoll.
- 2af28e603319 11.0 landed
-
Revise API for partition bound search functions.
- f724022d0ae0 11.0 landed
-
Revise API for partition_rbound_cmp/partition_rbound_datum_cmp.
- b0229235564f 11.0 landed
-
Fix possible crash in partition-wise join.
- f069c91a5793 11.0 cited
-
Refactor code for partition bound searching
- 9aef173163ae 11.0 landed
-
New C function: bms_add_range
- 84940644de93 11.0 landed
-
Add extensive tests for partition pruning.
- 8d4e70a63bf8 11.0 landed
-
Add null test to partition constraint for default range partitions.
- 7b88d63a9122 11.0 cited
-
Remove BufFile's isTemp flag.
- 11e264517dff 11.0 cited
-
Make OWNER TO subcommand mention consistent
- bf54c0f05c0a 11.0 cited
-
Fix index matching for operators with mixed collatable/noncollatable inputs.
- cb37c291060d 9.2.0 cited