Brian Cloutier f8fb7a27fb Don't copyObject into the wrong memory context ... utilityStmt sometimes (such as when it's inside of a plpgsql function) comes from a cached plan, which is kept in a child of the CacheMemoryContext. When we naively call copyObject we're copying it into a statement-local context, which corrupts the cached plan when it's thrown away.		2018-05-01 15:34:32 -07:00
..
backend	Don't copyObject into the wrong memory context	2018-05-01 15:34:32 -07:00
include	Removes large_table_shard_count GUC	2018-04-29 10:34:50 +02:00
test/regress	Don't copyObject into the wrong memory context	2018-05-01 15:34:32 -07:00