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

Re: PERSISTANT PREPARE (another point of view)

From: Milan Oparnica <milan(dot)opa(at)gmail(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: PERSISTANT PREPARE (another point of view)
Date: 2008-07-21 20:45:36
Message-ID: g62sgn$9b6$1@news.hub.org (view raw or flat)
Thread:
Lists: pgsql-sql
I found this link from IBM DB2 developers showing why PERSISTENT PREPARE 
is a good idea and how could it be implemented.

http://www.hoadb2ug.org/Docs/Favero20606.pdf

It seems that main benefit (beside efficiency) is memory.
Having number of connections all with dozens of PREPARED statements 
consumes lot of memory.

If we put these statements in global space (perhaps not even in RAM 
memory until needed) we could reuse optimization plans as well as 
physical space needed to store them.

I also found articles:

http://archives.postgresql.org/pgsql-hackers/2008-04/msg00867.php

and

http://archives.postgresql.org/pgsql-performance/2008-03/msg00480.php

all about users trying to explain PERSISTENT PREPARE (some refer to it 
as global prepare).


There are also some guys who actually made some code for PERSISTENT PREPARE:

http://archives.postgresql.org/pgsql-hackers/2008-03/msg01228.php
and
http://archives.postgresql.org/pgsql-hackers/2008-03/msg01219.php


PEOPLE NEED THIS FEATURE !!! It is not discovering the wheel but it will 
simplify DB programming and even gain some performance.

NONE OF POPULAR SQL DBMS (Oracle, MS SQL, MySQL, Postgre, INTERBASE, 
FIREBIRD) HAVE THIS FEATURE.

WHY ?

In response to

Responses

pgsql-sql by date

Next:From: Craig RingerDate: 2008-07-22 01:04:41
Subject: Re: PERSISTANT PREPARE (another point of view)
Previous:From: Emi LuDate: 2008-07-21 16:59:02
Subject: Re: Size or efficiency differences "varchar(128) vs. varchar(32)"

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