RE: [HACKERS] Cache query (PREPARE/EXECUTE)

From: Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] Cache query (PREPARE/EXECUTE)
Date: 2000-02-23 18:48:25
Message-ID: Pine.LNX.3.96.1000223192816.15013G-100000@ara.zf.jcu.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Thu, 24 Feb 2000, Hiroshi Inoue wrote:

> > This is overly conservative. It should be safe to destroy a plan tree
> > via freeObject() if it was created via copyObject() --- and that is
> > certainly how the plan would get into a permanent memory context.
> >
>
> I proposed the implementation of copyObject() which keeps the
> references among objects once before. It seems unnatural to me
> that such kind of implementation would never be allowed by this
> restriction.
>
> Why is memory context per plan bad ?

One context is more simple.

We talking about a *cache*. If exist interface for this cache and
all operations are with copy/freeObject it not has restriction.

For how action it will restriction?

The PlanCacheMemoryContext will store space only, it isn't space for
any action.

Karel Z.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2000-02-23 20:11:08 Re: [HACKERS] Cache query (PREPARE/EXECUTE)
Previous Message Jan Wieck 2000-02-23 18:22:16 Re: [HACKERS] Cache query (PREPARE/EXECUTE)