| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Misc. consequences of backend memory management changes |
| Date: | 2000-06-28 19:40:35 |
| Message-ID: | Pine.LNX.3.96.1000628213159.20347A-100000@ara.zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 28 Jun 2000, Karel Zak wrote:
>
> About context tree --- what will happen if in PG will exist some context
> that not will in context tree? Yes, it is curios question...explication:
> I have in the query cache contexts (for each plan) that are persisten (in
> shmem) across connection (and across TopMemoryContext live-time). How
> integrate this context to the contect tree? Or skip for this specific
> variant context type independent MemoryContextCreate and init this common
> part itself? - (I vote for this)
I a little speculate about it and I mean that query cache contexts can be
in separate contest tree based on master query cache context that is create
during global shmem initialization. Agree?
Karel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-06-28 23:53:03 | Re: Big 7.1 open items |
| Previous Message | pgsql-hackers | 2000-06-28 19:25:41 | Re: 7.0.2 on Solaris |