From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: CopyReadLineText optimization |
Date: | 2008-03-06 19:56:32 |
Message-ID: | 47D04C70.7070105@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Heikki Linnakangas wrote:
> Andrew Dunstan wrote:
>> I'm still a bit worried about applying it unless it gets some
>> adaptive behaviour or something so that we don't cause any serious
>> performance regressions in some cases.
>
> I'll try to come up with something. At the most conservative end, we
> could fall back to the current method on the first escape, quote or
> backslash character.
>
>
That's far too conservative, I think. Somewhere a bit short of your
observed breakeven point seems about right.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-03-06 20:02:16 | Re: 8.3 / 8.2.6 restore comparison |
Previous Message | Heikki Linnakangas | 2008-03-06 19:44:31 | Re: CopyReadLineText optimization |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-03-06 20:08:03 | Re: CopyReadLineText optimization |
Previous Message | Heikki Linnakangas | 2008-03-06 19:44:31 | Re: CopyReadLineText optimization |