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

Re: prepared transactions that persist across sessions?

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: mark(at)mark(dot)mielke(dot)cc
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: prepared transactions that persist across sessions?
Date: 2005-10-23 06:51:36
Message-ID: 20051023065136.GA12238@wolff.to (view raw or flat)
Thread:
Lists: pgsql-performance
On Sun, Oct 23, 2005 at 00:14:23 -0400,
  mark(at)mark(dot)mielke(dot)cc wrote:
> Hey all.
> 
> Please point me to a place I should be looking if this is a common
> question that has been debated periodically and at great length
> already. :-)

You probably want to read:
http://candle.pha.pa.us/main/writings/pgsql/sgml/runtime-config-query.html

Connection pooling might be another approach, since it should be possible
to reuse prepared statements when reusing a connection.

> I have a complex query. It's a few Kbytes large, and yes, I've already
> worked on reducing it to be efficient in terms of database design, and
> minimizing the expressions used to join the tables. Running some timing
> tests, I've finding that the query itself, when issued in full, takes
> around 60 milliseconds to complete on modest hardware. If prepared, and
> then executed, however, it appears to take around 60 milliseconds to
> prepare, and 20 milliseconds to execute. I'm not surprised. PostgreSQL
> is very likely calculating the costs of many, many query plans.

In response to

pgsql-performance by date

Next:From: Dennis BjorklundDate: 2005-10-23 10:04:07
Subject: Re: Need help in setting optimal configuration for a huge
Previous:From: markDate: 2005-10-23 04:14:23
Subject: prepared transactions that persist across sessions?

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