From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: XLogInsert |
Date: | 2009-12-09 07:04:16 |
Message-ID: | 3073cc9b0912082304p62bf94f1i95d03ac2c1741932@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Sep 13, 2009 at 10:42 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
> I've attached a patch which removes the iteration over the blocks to be
> backed-up from the critical section of XLogInsert. Now those blocks are
> only looped over in one piece of code which both computes the CRC and builds
> the linked list, rather than having parallel loops.
>
ok, i started to review this one...
what the patch is doing seems very obvious and doesn't break the
original logic AFAIUI (i could be wrong, this seems like chinese to me
;)
i made some tests archiving wal and recovering... crashing the server
and restarting... every test was running the regression tests,
don't know what else to do, ideas?
i haven't made any performance tests but it should gain something :),
maybe someone can make those tests?
if not, i will mark the patch as ready for committer some time in the
next hours...
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | 黄晓骋 | 2009-12-09 07:33:44 | 答复: questions about concurrency control in Postgresql |
Previous Message | Heikki Linnakangas | 2009-12-09 06:58:44 | Re: Streaming replication and non-blocking I/O |