| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
| Subject: | Re: [PATCH] A hook for session start |
| Date: | 2017-08-01 19:42:33 |
| Message-ID: | 20170801194233.atf4wf7y7xbrqqal@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-08-01 15:37:40 -0400, Peter Eisentraut wrote:
> On 7/21/17 12:59, Robert Haas wrote:
> > 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.
>
> Still nobody has presented a concrete use case so far.
Citus for example starts a background worker (performing
e.g. distributed deadlock detection) if the citus extension exists. We
atm need annoying hacks to do so when the first query is executed.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-08-01 19:55:17 | Re: [PATCH] A hook for session start |
| Previous Message | Peter Eisentraut | 2017-08-01 19:37:40 | Re: [PATCH] A hook for session start |