X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1D17552A38 for ; Mon, 9 May 2005 09:45:41 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 10014-06 for ; Mon, 9 May 2005 12:45:36 +0000 (GMT) Received: from mali.tis.hr (mali.tis.hr [213.191.155.197]) by svr1.postgresql.org (Postfix) with ESMTP id 1C25053659 for ; Mon, 9 May 2005 09:45:30 -0300 (ADT) Received: from 192.168.101.202 ([192.168.101.202]) by mali.tis.hr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 28KRRZCD; Mon, 9 May 2005 14:47:13 +0200 Subject: Re: Any experiance with PostgreSQL and SQLRelay From: Dario Lah To: pgsql-general@postgresql.org In-Reply-To: <427F53B0.4060906@lewczuk.com> References: <427F53B0.4060906@lewczuk.com> Content-Type: text/plain Organization: TIS.kis d.o.o Date: Mon, 09 May 2005 14:45:22 +0200 Message-Id: <1115642722.741.56.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-16) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200505/367 X-Sequence-Number: 77715 Not with Postgres, but i'm using it with PHP/Oracle (easier to install sqlrelay than oracle lient :) ) Anyway, it works ok and judging on comments on sqlrelay list, lots of people find it good solution for connection pooling. When I get some spare time, i'll probably rewrite postgres applications to work with sqlrelay/postgres. DL On Pon, 2005-05-09 at 14:12 +0200, Marek Lewczuk wrote: > Hi, > I need a db connection pooling in PHP. As far I know persistent > connections are not the best solution so I'm thinking about using > SQLRelay. Does anyone have any experience using PostgreSQL + PHP + > SQLRelay ? Maybe you know other "connection pooling" solutions for PHP ? > > Thanks in advance. > > ML > > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match