| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: What exactly is our CRC algorithm? |
| Date: | 2014-11-04 13:40:36 |
| Message-ID: | 20141104134036.GO28295@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-11-04 08:21:13 -0500, Robert Haas wrote:
> On Tue, Nov 4, 2014 at 4:47 AM, Heikki Linnakangas
> <hlinnakangas(at)vmware(dot)com> wrote:
> > I hear none, so committed with some small fixes.
>
> Are you going to get the slice-by-N stuff working next, to speed this up?
I don't plan to do anything serious with it, but I've hacked up the crc
code to use the hardware instruction. The results are quite good - crc
vanishes entirely from the profile for most workloads. It's still
visible for bulk copy, but that's pretty much it.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-11-04 13:41:56 | Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code |
| Previous Message | Andres Freund | 2014-11-04 13:38:49 | Re: tracking commit timestamps |