Re: Still something fishy in the fastpath lock stuff - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Still something fishy in the fastpath lock stuff
Date
Msg-id CA+TgmoaVm1Q55ukRs+p_A6SLJ94QnHTmXvoiE+Jc5nyA96wZ3Q@mail.gmail.com
Whole thread Raw
In response to Re: Still something fishy in the fastpath lock stuff  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Still something fishy in the fastpath lock stuff  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Mar 26, 2014 at 12:59 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> It seems to me that the simplest thing to do might be
> just this:
>
> -static FastPathStrongRelationLockData *FastPathStrongRelationLocks;
> +static volatile FastPathStrongRelationLockData *FastPathStrongRelationLocks;
>
> Do you see any problem with that approach?

Hearing nothing, I went ahead and did this.  I see that the failure on
prairiedog only occurred once, so I don't know how we'll know whether
this fixed the problem that caused that failure or merely fixed a
problem that could cause a failure, but I'm not sure what else we can
really do at this point.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "Behn, Edward (EBEHN)"
Date:
Subject: Re: Array of composite types returned from python
Next
From: Robert Haas
Date:
Subject: Re: issue log message to suggest VACUUM FULL if a table is nearly empty