| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: Log inability to lock pages during vacuum |
| Date: | 2014-12-01 02:46:51 |
| Message-ID: | 547BD69B.5050900@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/10/14, 7:52 PM, Tom Lane wrote:
> On the whole, I'm +1 for just logging the events and seeing what we learn
> that way. That seems like an appropriate amount of effort for finding out
> whether there is really an issue.
Attached is a patch that does this.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Log-cleanup-lock-acquisition-failures-in-vacuum.patch | text/plain | 3.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip kumar | 2014-12-01 06:48:41 | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |
| Previous Message | Peter Geoghegan | 2014-12-01 01:49:51 | Re: 9.5: Better memory accounting, towards memory-bounded HashAgg |