From: | Japin Li <japinli(at)hotmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Song JinZhou <tsinghualucky912(at)foxmail(dot)com> |
Subject: | Re: Support event trigger for logoff |
Date: | 2024-04-22 13:24:29 |
Message-ID: | ME3P282MB31668D70A037A2189ABF2419B6122@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 20 Apr 2024 at 01:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Japin Li <japinli(at)hotmail(dot)com> writes:
>> I see [1] has already implemented on login event trigger, why not implement
>> the logoff event trigger?
>
> What happens if the session crashes, or otherwise fails unexpectedly?
>
I am currently unsure how to handle such situations, but I believe it is not
only for logoff events.
>> Here is a problem with the regression test when using \c to create a new
>> session, because it might be running concurrently, which may lead to the
>> checking being unstable.
>
>> Any thoughts?
>
> Let's not go there at all. I don't think there's enough field
> demand to justify dealing with this concept.
>
Thanks for your point out this for me.
--
Regards,
Japin Li
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-04-22 13:25:15 | Re: Support a wildcard in backtrace_functions |
Previous Message | Hayato Kuroda (Fujitsu) | 2024-04-22 12:54:10 | RE: Slow catchup of 2PC (twophase) transactions on replica in LR |