| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Still something fishy in the fastpath lock stuff |
| Date: | 2014-03-31 18:44:45 |
| Message-ID: | CA+TgmoaVm1Q55ukRs+p_A6SLJ94QnHTmXvoiE+Jc5nyA96wZ3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 26, 2014 at 12:59 AM, Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-03-31 18:54:10 | Re: issue log message to suggest VACUUM FULL if a table is nearly empty |
| Previous Message | Behn, Edward (EBEHN) | 2014-03-31 18:43:51 | Re: Array of composite types returned from python |