From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | MauMau <maumau307(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [RFC] Should smgrtruncate() avoid sending sinval message for temp relations |
Date: | 2015-02-23 15:47:39 |
Message-ID: | 20150223154739.GE30784@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2014-07-26 18:16:01 +0200, Andres Freund wrote:
> On 2014-07-26 11:32:24 -0400, Tom Lane wrote:
> > "MauMau" <maumau307(at)gmail(dot)com> writes:
> > > [ sinval catchup signal -> ProcessCatchupEvent -> WaitLatch -> deadlock ]
> >
> > Ugh.
> >
> > One line of thought is that it's pretty unsafe to be doing anything
> > as complicated as transaction start/commit in a signal handler, even one
> > that is sure it's not interrupting anything else.
>
> Yea, that's really not nice.
MauMau, we don't do this anymore. Could you verify that the issue is
fixed for you?
I'd completely forgotten that this thread made me work on moving
everything complicated out of signal handlers...
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2015-02-23 15:48:25 | Re: Primary not sending to synchronous standby |
Previous Message | Thom Brown | 2015-02-23 15:44:43 | Re: Primary not sending to synchronous standby |