From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | <hs(at)cybertec(dot)at>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PREPARE / EXECUTE |
Date: | 2002-10-23 18:58:13 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961ED1@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The idea is not to have it accross multiple backends and having it in
> sync with the tables in the database. This is not the point.
> My problem is that I have seen many performance critical applications
> sending just a few complex queries to the server. The problem is: If you
> have many queries where the relation "time planner"/"time executor" is
> very high (eg. complex joins with just one value as the result).
The standard approach to such a scenario would imho be to write stored procedures
for the complex queries (e.g. plpgsql) and use that from the client.
Maybe even eliminate a few ping pongs between client and server.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Hans-Jürgen Schönig | 2002-10-23 19:09:45 | Re: PREPARE / EXECUTE |
Previous Message | Tom Lane | 2002-10-23 18:46:33 | Re: 'epoch'::timestamp and Daylight Savings |