public inbox for [email protected]  

help / color / mirror / Atom feed

From: Japin Li <[email protected]>
To: Tom Lane <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Song JinZhou <[email protected]>
Subject: Re: Support event trigger for logoff
Date: Mon, 22 Apr 2024 21:24:29 +0800
Message-ID: <ME3P282MB31668D70A037A2189ABF2419B6122@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <[email protected]>
References: <ME3P282MB316614DBFF1CB7F7EB4C6C0AB60D2@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM>
	<[email protected]>


On Sat, 20 Apr 2024 at 01:36, Tom Lane <[email protected]> wrote:
> Japin Li <[email protected]> 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

view thread (3+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Support event trigger for logoff
  In-Reply-To: <ME3P282MB31668D70A037A2189ABF2419B6122@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox