From: Tom Lane <tgl@sss.pgh.pa.us>
To: Japin Li <japinli@hotmail.com>
cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
        Song JinZhou <tsinghualucky912@foxmail.com>
Subject: Re: Support event trigger for logoff
In-reply-to: <ME3P282MB316614DBFF1CB7F7EB4C6C0AB60D2@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM>
References: <ME3P282MB316614DBFF1CB7F7EB4C6C0AB60D2@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM>
Comments: In-reply-to Japin Li <japinli@hotmail.com>
	message dated "Fri, 19 Apr 2024 23:46:10 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2174634.1713548194.1@sss.pgh.pa.us>
Date: Fri, 19 Apr 2024 13:36:34 -0400
Message-ID: <2174635.1713548194@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2174635.1713548194%40sss.pgh.pa.us>
Precedence: bulk

Japin Li <japinli@hotmail.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?

> 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.

			regards, tom lane