|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Andres Freund <andres(at)anarazel(dot)de>|
|Cc:||Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Strange failure in LWLock on skink in REL9_5_STABLE|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-09-20 23:15:45 -0400, Tom Lane wrote:
> That shouldn't be relevant here - I'm not running the buildfarm from an
> interactive session and then logging out. So that code shouldn't
Well, the reason that systemd behavior is so brain-dead is exactly that
it will trigger against processes that you didn't launch interactively.
IIUC, you just have to log in and out of that account, and anything that
was running in the background (eg cron jobs) under the same userID gets
> I've made sure that the setting is off now however, I'm not
> trusting the related logic very much...
Was it on before?
regards, tom lane
|Next Message||Andrey Lepikhov||2018-09-21 03:52:10||Re: [WIP] [B-Tree] Retail IndexTuple deletion|
|Previous Message||Andres Freund||2018-09-21 03:36:12||Re: Strange failure in LWLock on skink in REL9_5_STABLE|