Re: Partitioning option for COPY

Emmanuel Cecchet <manu@asterdata.com> writes:
> Actually the list is supposed to stay around between statement 
> executions. You don't want to restart with a cold cache at every 
> statement so I really want this structure to stay in memory at a more 
> global level.

Cache?  Why do you need a cache for COPY?  Repeated bulk loads into the
same table within a single session doesn't seem to me to be a case that
is common enough to justify a cache.

(BTW, the quoted code seems to be busily reinventing OID Lists.  Don't
do that.)
        regards, tom lane