| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
| Date: | 2016-04-12 04:32:13 |
| Message-ID: | 4369.1460435533@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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. Maybe convert that into
init_spin_delay(SpinDelayStatus *target, whatever-the-other-arg-is) ?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-04-12 05:00:38 | Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
| Previous Message | Andres Freund | 2016-04-12 04:03:35 | Re: Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arcadiy Ivanov | 2016-04-12 04:36:42 | Parser extensions (maybe for 10?) |
| Previous Message | Andres Freund | 2016-04-12 04:03:35 | Re: Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |