| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Improve concurrency of foreign key locking |
| Date: | 2013-01-23 16:23:32 |
| Message-ID: | 51000E84.7050905@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 01/23/2013 10:12 AM, Alvaro Herrera wrote:
> Improve concurrency of foreign key locking
>
>
It looks like isolation_tester.c needs a few calls to fflush(stderr)
(basically in those places where it won't be exiting right afterwards.)
This would probably account for the windows buildfarm failure I see on
frogmouth.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-01-23 16:32:17 | pgsql: isolationtester: add a few fflush(stderr) calls |
| Previous Message | Robert Haas | 2013-01-23 16:05:39 | pgsql: Clarify that connection parameters aren't totally meaningless fo |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-01-23 16:40:44 | Re: Prepared statements fail after schema changes with surprising error |
| Previous Message | Fujii Masao | 2013-01-23 16:21:07 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |