Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.
От | Andres Freund |
---|---|
Тема | Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
Дата | |
Msg-id | 20160412050038.ua2avkwi6dxxcjhx@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.
Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
Список | pgsql-hackers |
On 2016-04-12 00:32:13 -0400, Tom Lane wrote: > I wrote: > > This commit has broken buildfarm member gaur, and no doubt pademelon > > will be equally unhappy once it catches up to HEAD. > > Spoke too soon, actually: pademelon did not get as far as initdb. > > cc: "bufmgr.c", line 4032: error 1521: Incorrect initialization. > cc: "bufmgr.c", line 4058: error 1521: Incorrect initialization. > > Apparently, assigning the result of init_spin_delay() is not as portable > as you thought. Hm. I'm not sure why not though? Is it because delayStatus isn't static or global scope? > Maybe convert that into init_spin_delay(SpinDelayStatus *target, > whatever-the-other-arg-is) ? Too bad, my compiler generates a bit nicer code for the current version. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: