| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LWLock deadlock and gdb advice |
| Date: | 2015-08-02 15:05:06 |
| Message-ID: | 20150802150506.GH11473@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-08-02 17:04:07 +0200, Andres Freund wrote:
> I've attached a version of the patch that should address Heikki's
> concern. It imo also improves the API and increases debuggability by not
> having stale variable values in the variables anymore. (also attached is
> a minor optimization that Heikki has noticed)
...
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-issues-around-the-variable-support-in-the-lwlock.patch | text/x-patch | 13.8 KB |
| 0002-Micro-optimize-LWLockAttemptLock-a-bit.patch | text/x-patch | 2.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Shaplov | 2015-08-02 16:03:02 | pageinspect patch, for showing tuple data |
| Previous Message | Andres Freund | 2015-08-02 15:04:07 | Re: LWLock deadlock and gdb advice |