The following bug has been logged online:
Bug reference: 4637
Logged by: chetan
Email address: cheth...@inat.in
PostgreSQL version: plus 8.3
Operating system: windows xp
Description:FATAL: sorry, too many clients already
Details:
2009-02-03 12:41:58,109 INFO [STDOU
The following bug has been logged online:
Bug reference: 4638
Logged by: Bjoern Weitzig
Email address: weit...@supportgis.de
PostgreSQL version: 8.3.5
Operating system: Windows
Description:Bug with Geometry in Array
Details:
System: PostgreSQL 8.3.5, compiled by Vis
"Bjoern Weitzig" writes:
> I use arrays like "select array(select n from a)". This works well except of
> the case with geometry as datatype.
The geometry type intentionally uses ':' as the array delimiter. It
seems like a good bet that the JDBC driver you're using doesn't expect
anything but '
chetan wrote:
The following bug has been logged online:
Bug reference: 4637
Logged by: chetan
Email address: cheth...@inat.in
PostgreSQL version: plus 8.3
Operating system: windows xp
Description:FATAL: sorry, too many clients already
Details:
2009-02-03 12:41:58,1
I've completed my test for changes to the Windows implementation of
pgkill. I ran two clients constantly doing a pair of notifications,
with one client subscribing to those events. I ran the test for 90
hours. I found 760 cases where the CallNamedPipe function initially
failed, but succeeded
On Tue, Feb 03, 2009 at 11:31:31AM -0700, Joshua Tolley wrote:
> Unless, of course,
> I'm missing something.
Yep, I was missing something. I didn't realize ROLLBACK TO SAVEPOINT
didn't destroy the newer savepoint like RELEASE SAVEPOINT does. Adding
RELEASE SAVEPOINT calls to my test script makes i
The SAVEPOINT documentation says that a new savepoint created with the
same name as an existing savepoint masks but does not destroy the old
savepoint, and rolling back to the savepoint will then make the old
savepoint available for RELEASE SAVEPOINT and ROLLBACK TO SAVEPOINT
calls. 8.3.5 and my 8.
