| From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
|---|---|
| To: | vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Improvements in Copy From |
| Date: | 2020-09-07 07:49:31 |
| Message-ID: | CALAY4q85-V46UojNjKTuVreuAMgf8xGYbPyqZQK7oa82MrMiWQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Vignesh
On Wed, Jul 1, 2020 at 3:46 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> Hi,
>
> While reviewing copy from I identified few improvements for copy from
> that can be done :
> a) copy from stdin copies lesser amount of data to buffer even though
> space is available in buffer because minread was passed as 1 to
> CopyGetData, Hence it only reads until the data read from libpq is
> less than minread. This can be fixed by passing the actual space
> available in buffer, this reduces the unnecessary frequent calls to
> CopyGetData.
>
why not applying the same optimization on file read ?
> c) Copy from reads header line and do nothing for the header line, we
> need not clear EOL & need not convert to server encoding for the
> header line.
>
We have a patch for column matching feature [1] that may need a header line
to be further processed. Even without that I think it is preferable to
process the header line for nothing than adding those checks to the loop,
performance-wise.
regards
Surafel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | k.jamison@fujitsu.com | 2020-09-07 08:03:05 | RE: [Patch] Optimize dropping of relation buffers using dlist |
| Previous Message | David Rowley | 2020-09-07 07:47:59 | Re: Optimising compactify_tuples() |