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

Re: Oracle vs PostgreSQL in real life

From: Jean-Paul ARGUDO <jean-paul(dot)argudo(at)idealx(dot)com>
To: Hannu Krosing <hannu(at)itmeedia(dot)ee>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Oracle vs PostgreSQL in real life
Date: 2002-02-28 13:39:47
Message-ID: 20020228143947.B8534@singer.ird.idealx.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> > it seems that on every commit, the cursor is closed... and re-opened with
> > new
> > variables'values
> 
> I think that currently the only way to reuse query plans would be migrating
> some
> of your logic to backend and using SPI prepared statements.
> 
> > btw, as many asked me, queries are VERY simple, there is only a few
> queries.
> > Each query works on one table at a time. no joins for example. Only
> massive bulk
> > work with CURSORS.
> 
> Again, can't some of it be moved to backend, either using PL/PgSQL or C (or
> pltcl, plperl, plpython ;)
> 


OK.


We read all the " Chapter 21. Server Programming Interface" with SPI doc.

This seems _really_ interresting, make me remember of outline statments in
Oracle.

So:

1) how to find some sample code? are SPI statments can be called from
/into ecpg?

2) if prepared statments and stored execution plan exist, why can't thos be used
from any client interface or simple sql?

3) You tell us we can "move to the backend" some queries: do you mean we would
have better performances with stored functions in plpgsql? 

Thanks a lot Hannu, I promise to stop soon with questions :-)

This is _so_ important for us..

Best regards & wishes.

--
Jean-Paul ARGUDO

In response to

Responses

pgsql-hackers by date

Next:From: Rod TaylorDate: 2002-02-28 13:56:36
Subject: Re: Arch (was RE: Refactoring of command.c )
Previous:From: Hannu KrosingDate: 2002-02-28 13:24:15
Subject: Re: Oracle vs PostgreSQL in real life

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