| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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-06 19:36:54 |
| Message-ID: | 20171006193653.GG1251@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 06, 2017 at 08:51:53PM +0200, Pavel Stehule wrote:
> 2017-10-06 20:39 GMT+02:00 Nico Williams <nico(at)cryptonector(dot)com>:
> > On Fri, Oct 06, 2017 at 06:37:57PM +0200, Pavel Stehule wrote:
> > > When we talked about this topic, there are two issues:
> > >
> > > a) probably not too hard issue - some internal data can be in session sys
> > > cache.
> > >
> > > b) the session sys data should be visible on SQL level too (for some
> > tools
> > > and consistency) - it is hard task.
> >
> > Can you expand on this?
>
> If global temporary tables should be effective, then you have not have
> modify system catalogue after creating. But lot of processes requires it -
> ANALYZE, query planning.
But the nice thing about them is that you need only create them once, so
leave them in the catalog. Stats about them should not be gathered nor
stored, since they could be different per-session.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-10-06 19:37:09 | separate serial_schedule useful? |
| Previous Message | Robert Haas | 2017-10-06 19:34:05 | Re: Partition-wise join for join between (declaratively) partitioned tables |