| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Jim Mlodgenski <jimmy76(at)gmail(dot)com>, 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-10-05 20:31:40 |
| Message-ID: | 20171005203138.GY1251@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 01, 2017 at 03:36:23PM -0400, Peter Eisentraut wrote:
> On 7/21/17 13:14, Jim Mlodgenski wrote:
> > When I first saw this thread, my initial thought of a use case is to
> > prepare some key application queries so they are there and ready to go.
> > That would need to be before the ExecutorStart_hook or
> > ProcessUtility_hook if an app would just want to execute the prepared
> > statement.
>
> Isn't that what the preprepare extension does already?
more generic facility -> more useful
My use case is to pre-create TEMP schema elements that VIEWs, FUNCTIONs,
and TRIGGERs, might need.
Nico
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-10-05 21:02:38 | Re: parallelize queries containing initplans |
| Previous Message | Nico Williams | 2017-10-05 20:30:06 | Re: [PATCH] A hook for session start |