Re: Force lookahead in COPY FROM parsing - Mailing list pgsql-hackers

From John Naylor
Subject Re: Force lookahead in COPY FROM parsing
Date
Msg-id CAFBsxsFQwDMmCcLCWuVPWX=SQvu0dtr6urPDV45sUUNVOC=MtA@mail.gmail.com
Whole thread Raw
Responses Re: Force lookahead in COPY FROM parsing  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
The cfbot thinks this patch no longer applies, but it works for me, so still set to RFC. It looks like it's because the thread to remove the v2 FE/BE protocol was still attached to the commitfest entry. I've deleted that, so let's see if that helps.

To answer the side question of whether it makes any difference in performance, I used the blackhole AM [1] to isolate the copy code path as much as possible. Forcing lookahead seems to not make a noticeable difference (min of 5 runs):

master:
306ms

force lookahead:
304ms

--

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Reduce the time required for a database recovery from archive.
Next
From: David Steele
Date:
Subject: Re: Implement for window functions