Skip site navigation (1) Skip section navigation (2)

Re: PERSISTANT PREPARE (another point of view)

From: chester c young <chestercyoung(at)yahoo(dot)com>
To: milan(dot)opa(at)gmail(dot)com, sql pgsql <pgsql-sql(at)postgresql(dot)org>
Subject: Re: PERSISTANT PREPARE (another point of view)
Date: 2008-07-26 00:32:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
1. like the idea because right now I'm having to track which prepared statement (sets) are in which session.  using xcache to track this, but little bit dangerous.  could query the database first but the whole idea is to take a load off the db.

2. perhaps "global" could mean simply that the definition is global - if called for session and not exist in session, then session prepares it first from the global def.  there would need to be a back reference in case the global def was changed or dropped.

3. don't understand your statement about how prepared statements can be used as subqueries - you mean something like

  select .. from tab1 t1 where t1.col1 in( exec prep1(..) )

or exactly what?


In response to


pgsql-sql by date

Next:From: Ole EkerhovdDate: 2008-07-26 05:24:55
Subject: Test if a table is present
Previous:From: Pavel StehuleDate: 2008-07-25 19:07:18
Subject: Re: PERSISTANT PREPARE (another point of view)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group