Hi,
Finally i found the problem of slow backup/restore, i´m only instaled de
Windows 2000 Service Pack 4... :)
Thanks to all
Franklin
-Mensagem original-
De: Richard Huxton [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 30 de
novembro de 2005 14:28
Para: Franklin Haut
Cc:
Em Sex, 2006-01-20 às 15:34 -0600, Jim C. Nasby escreveu:
On Fri, Jan 20, 2006 at 08:38:23PM +0100, Rikard Pavelic wrote:
This would solve problems with prepare which is per session, so for
prepared function to be
optimal one must use same connection.
If you're dealing with something
August Zajonc wrote:
Alessandro Baretta wrote:
Alessandro,
I've very much enjoyed reading your thoughts and the problem your facing
and everyone's responses.
Thank you for your interest, Agust.
Since you control the middle layer, could you not use a cookie to keep a
cursor open on the
Hi, Marcos,
Marcos wrote:
This one was my doubt, perhaps in based desktop applications this is
true, but in web applications this is not the re-connecting is
constant :(.
If this is true, then you have a much bigger performance problem than
query plan preparation.
You really should consider
Hi Markus
You really should consider using a connection pool (most web application
servers provide pooling facilities) or some other means to keep the
connection between several http requests.
Yes. I'm finding a connection pool, I found the pgpool but yet don't
understand how it's work I'm go
I don't think pgpool is what you need. If I understand pgpool
correctly, pgpool lets you pool multiple postgres servers together. You
are just looking for database connection pooling.
A simple connection pool is basically just an application wide list of
connections. When a client needs a
On Mon, 23 Jan 2006 10:23:17 -0600
Dave Dutcher [EMAIL PROTECTED] wrote:
I don't think pgpool is what you need. If I understand pgpool
correctly, pgpool lets you pool multiple postgres servers together.
You are just looking for database connection pooling.
While pgpool can let you pool
=?ISO-8859-1?Q?=DCmit_=D6ztosun?= [EMAIL PROTECTED] writes:
Our application uses typical queries similar to following (very simplified):
SELECT
part_id,
part_name,
(SELECT
SUM(amount) FROM part_movements M
WHERE P.part_id =3D M.part_id
) as part_amount
FROM parts P
ORDER BY
unsubscribe
