Re: rare avl shutdown slowness (related to signal handling)

From: Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: rare avl shutdown slowness (related to signal handling)
Date: 2015-04-07 23:15:21
Message-ID: CAJjS0u24Op7GcpQtMGj=kJ6p4jZyf9ROwKNJcaDtx1-wMbvM+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 7, 2015 at 4:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Indeed, which is why I think a patch for this issue should not introduce
> a new mode/context in which proc_exit() is executed.

Agree. Along this line, we can add an on_proc_exit hook simply
ereport("we are exiting") there. In this way, we reuse all shields
proc_exit() already has. Abuse?

Regards,
Qingqing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2015-04-07 23:52:07 Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Previous Message Tom Lane 2015-04-07 23:01:59 Re: rare avl shutdown slowness (related to signal handling)