From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Nikolai Zhubr <n-a-zhubr(at)yandex(dot)ru>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Server-side hooks for user session start and session end |
Date: | 2015-09-26 19:03:51 |
Message-ID: | CAKFQuwaBaJbXUAWwQCRgquKaejGe1nEG-AwykKP_pSfp9pD+aA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Saturday, September 26, 2015, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com <javascript:;>> writes:
> > 2015-09-26 19:53 GMT+02:00 Nikolai Zhubr <n-a-zhubr(at)yandex(dot)ru
> <javascript:;>>:
> >> And the events of session start and session end would seem quite generic
> >> and usefull anyway?
>
> > I don't know. I am pretty sceptical - from my experience this request was
> > related to unhappy designed projects.
>
> A session-end hook seems pretty problematic to me: you simply cannot
> guarantee that it will run at all. (Consider process crash or server
> abort cases.) So anything built on the assumption that it gets to run
> at session end is going to be inherently unreliable.
>
>
Or even "reset session" as is often used by connection poolers depending on
what semantics are trying to be captured.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolai Zhubr | 2015-09-27 00:12:18 | Re: Server-side hooks for user session start and session end |
Previous Message | Pavel Stehule | 2015-09-26 18:41:52 | Re: Server-side hooks for user session start and session end |