Re: [PATCH] A hook for session start
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: Yugo Nagata <nagata@sraoss.co.jp>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Fabrízio de Royes Mello <fabriziomello@gmail.com>
Date: 2017-07-21T16:59:04Z
Lists: pgsql-hackers
On Fri, Jul 21, 2017 at 11:10 AM, Craig Ringer <craig@2ndquadrant.com> wrote: > Don't we have that timestamp already? > > What practical use cases are there for acting post-auth but that can't wait > until the user tries to do something? Have, yes; record, no. > Can a user do anything remotely interesting or useful without hitting either > ExecutorStart_hook or ProcessUtility_hook? They can parse queries I guess > but you could just set your hook up in the parser instead. If you hook the > parser all they can do is open an idle session and sit there... That's an exceedingly-weak argument for rejecting this patch. The fact that you can probably hack around the lack of a hook for most reasonable use cases is not an argument for having a hook that does what people actually want to do. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add hooks for session start and session end, take two
- e788bd924c19 13.0 landed