Re: isolation check takes a long time
От | Andrew Dunstan |
---|---|
Тема | Re: isolation check takes a long time |
Дата | |
Msg-id | CAD5tBcJ53KaefcFUv6y=7B1oSS=bMFyfej05xNEgR_U9ghwTNA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: isolation check takes a long time (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: isolation check takes a long time
|
Список | pgsql-hackers |
On Fri, Jul 13, 2012 at 6:25 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
I'm looking into that. But given that the default is to set max_prepared_transactions to 0, shouldn't we just remove that test from the normal installcheck schedule?
We could provide an alternative schedule that does include it.
cheers
andrew
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 slowerI think the "prepared transactions" test is the one that takes the
> 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?
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?
I'm looking into that. But given that the default is to set max_prepared_transactions to 0, shouldn't we just remove that test from the normal installcheck schedule?
We could provide an alternative schedule that does include it.
cheers
andrew
В списке pgsql-hackers по дате отправления: