Looking at the profile for COPY and then a profile for CREATE TABLE AS
SELECT (CTAS) there is clearly too much overhead caused by inserting the
rows one at a time.
Flat profile of CTAS: (2 cols of this output removed for clarity)
Each sample counts as 0.01 seconds.
% cumulative self
Simon Riggs [EMAIL PROTECTED] writes:
1.41 7.25 0.13 1029CacheInvalidateHeapTuple
which together account for more than 50% of CPU.
The second column is cumulative percentage (the third column is self time).
So together this function and all the items above it account for
On Tue, 2008-02-26 at 15:25 +, Gregory Stark wrote:
Simon Riggs [EMAIL PROTECTED] writes:
1.41 7.25 0.13 1029CacheInvalidateHeapTuple
which together account for more than 50% of CPU.
The second column is cumulative percentage (the third column is self time).
So
