Joshua Lockerman 4b42b301a7 Free ChunkInsertStates when the es_per_tuple_exprcontext is freed ...

Instead of freeing ChunkInsertStates immediately when flushed from the
SubspaceStore, defer the freeing until the es_per_tuple_exprcontext is
being cleaned up. This ensures that pointers into the CIS don't become
invalidated without us freeing any of postgres's memory, like we were
doing in the prior fix; this fixes a segfault in COPY.

In the normal INSERT case these frees happen at approximately the same
time so there should be no regression in memory usage, while if there
was a delay in freeing the es_per_tuple_exprcontext our old strategy of
clearing the context ourselves was invalid.

2018-12-14 16:08:40 -05:00

..

alter.tsv

Improve handling of column settings

2018-07-24 14:11:53 -04:00

copy_data.csv

Free ChunkInsertStates when the es_per_tuple_exprcontext is freed

2018-12-14 16:08:40 -05:00

ds1_dev1_1.tsv

use PostgreSQL's own hash_any function as default partfunc;

2017-04-29 18:31:44 -04:00