From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: isolation check takes a long time |
Date: | 2012-07-13 22:25:26 |
Message-ID: | 1342218222-sup-8473@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Andrew Dunstan's message of vie jul 13 16:05:37 -0400 2012:
> Why does the isolation check take such a long time? On some of my slower
> buildfarm members I am thinking of disabling it because it takes so
> long. This single test typically takes longer than a full serial
> standard regression test. Is there any way we could make it faster?
I think the "prepared transactions" test is the one that takes the
longest. Which is a shame when prepared xacts are not enabled, because
all it does is throw millions of "prepared transactions are not enabled"
errors. There is one other test that takes very long because it commits
a large amount of transactions. I found it to be much faster if run
with fsync disabled.
Maybe it'd be a good idea to disable fsync on buildfarm runs, if we
don't already do so?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-07-13 22:36:23 | Re: [PATCH] lock_timeout and common SIGALRM framework |
Previous Message | Tom Lane | 2012-07-13 22:23:31 | Re: [PATCH] lock_timeout and common SIGALRM framework |