Re: reducing isolation tests runtime
От | Andres Freund |
---|---|
Тема | Re: reducing isolation tests runtime |
Дата | |
Msg-id | 20181204205006.rvbbsbjax3vpm5by@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: reducing isolation tests runtime (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Hi, On 2018-12-04 15:45:39 -0500, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: > > I'd like to see this revived, getting a bit tired waiting longer and > > longer to see isolationtester complete. Is it really a problem that we > > require a certain number of connections? Something on the order of 30-50 > > connections ought not to be a real problem for realistic machines, and > > if it's a problem for one, they can use a serialized schedule? > > The longstanding convention in the main regression tests is 20 max. > Is there a reason to be different here? It's a bit less obvious from the outside how many connections a test spawn - IOW, it might be easier to maintain the schedule if the cap isn't as tight. And I'm doubtful that there's a good reason for the 20 limit these days, so going a bit higher seems reasonable. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: