Robert Haas wrote:
> On Fri, Feb 18, 2011 at 9:35 PM, Bruce Momjian wrote:
> > Was this implemented? ?Is it a TODO?
>
> It's not entirely clear to me that there's a meaningful win here.
> Speeding up COPY is already on the TODO list, with this link:
>
> http://archives.postgresql.org/pgsql-hacke
On Fri, Feb 18, 2011 at 9:35 PM, Bruce Momjian wrote:
> Was this implemented? Is it a TODO?
It's not entirely clear to me that there's a meaningful win here.
Speeding up COPY is already on the TODO list, with this link:
http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php
...and i
Was this implemented? Is it a TODO?
---
Heikki Linnakangas wrote:
> I'm reviving the effort I started a while back to make COPY faster:
>
> http://archives.postgresql.org/pgsql-patches/2008-02/msg00100.php
> http://archive
Heikki Linnakangas writes:
> Ok. If we have to, we can keep that, it just requires more
> programming. After searching for a \n, we can peek at the previous byte to
> check if it's a backslash (and if it is, the one before that to see if it's
> a backslash too, and so forth until we find a non-bac
Heikki Linnakangas writes:
> On 26/08/10 22:16, Tom Lane wrote:
>> I think this is likely to break apps that have worked for years. I
>> can't get excited about doing that in return for an "0-10%" speedup
>> that might only materialize on some platforms. If the numbers were
>> better, it'd be wo
On 26/08/10 22:16, Tom Lane wrote:
Heikki Linnakangas writes:
* instead of the byte-at-a-time loop in CopyReadLineText(), use memchr()
to find the next NL/CR character. This is where the speedup comes from.
That seems like the speedup, if any, would be extremely
platform-dependent. What have
Heikki Linnakangas writes:
> * we perform possible encoding conversion early, one input block at a
> time, rather than after splitting the input into lines. This allows us
> to assume in the later stages that the data is in server encoding,
> allowing us to search for the '\n' byte without worr
I'm reviving the effort I started a while back to make COPY faster:
http://archives.postgresql.org/pgsql-patches/2008-02/msg00100.php
http://archives.postgresql.org/pgsql-patches/2008-03/msg00015.php
The patch I now have is based on using memchr() to search end-of-line.
In a nutshell:
* we pe
