From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ERROR during end-of-xact/FATAL |
Date: | 2013-11-28 19:28:23 |
Message-ID: | CA+TgmobywKtw34AQqvx2Uks9k3UgrNC3spE18+FkPavOM6yPwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 28, 2013 at 10:10 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Robert Haas escribió:
>> On Wed, Nov 6, 2013 at 9:40 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>> > Noah Misch wrote:
>> >> Incomplete list:
>> >>
>> >> - If smgrDoPendingDeletes() finds files to delete, mdunlink() and its callee
>> >> relpathbackend() call palloc(); this is true in all supported branches. In
>> >> 9.3, due to commit 279628a0, smgrDoPendingDeletes() itself calls palloc().
>> >> (In fact, it does so even when the pending list is empty -- this is the only
>> >> palloc() during a trivial transaction commit.) palloc() failure there
>> >> yields a PANIC during commit.
>> >
>> > I think we should fix this routine to avoid the palloc when not necessary.
>> > That initial palloc is pointless.
>
> Here's a trivial patch we could apply to 9.3 immediately. Anything else
> such as the ideas proposed below would require more effort than anyone
> can probably spend here soon.
Yeah, this seems like a good thing to do for now.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-11-28 19:35:23 | Re: lock on object is already held |
Previous Message | Robert Haas | 2013-11-28 19:25:28 | Re: Marginal performance improvement for fast-path locking |