> The following bug has been logged online:
>
> Bug reference: 1065
> Logged by: R. Lemos
>
> The JDBC2 pooled datasource(org.postgresql.jdbc2.optional.ConnectionPool),
> although implements java.io.Serializable, cannot be correctly serialized.
> Its superclass does not implement ja
I fixed this problem by installing the package crypt under the LIB
category in cygwin.
Thanks,
John Wright
I compiled with zlib 1.2.1 and can't reproduce the error, but that
probably has nothing to do with it. It looks like there's a sleep right
before the test that failed. Perhaps it didn't sleep long enough? As I
said, I haven't been able to reproduce the problem but I thought I'd
send it on in
Hi,
Postgres is part of the openSource repository DSpace which we are running here
at ANU. I upgraded from 7.4 to 7.4.1 on 17 January. Today (21/1) it appears
that either the number of connections has been reached (which is not possible
on my local install) or the database itself has locked up.
POSTGRESQL BUG REPORT TEMPLATE
Your name : Tanya Mamedalin
Your email address : [EMAIL PROTECTED]
When grilled further on (Sat, 24 Jan 2004 15:54:07 -0500),
Tom Lane <[EMAIL PROTECTED]> confessed:
> > A custom Perl 5.6.1, DBI 1.30, DBD::Pg 1.22 script on Solaris 5.8.
> > Using pgsql client version 7.3.3. I'm thinking it may be related to
> > my forking? My program has a db connection, which
I have the following tables and indexes
CREATE TABLE cddb
(
id integer PRIMARY KEY,
/* artist name */
name text,
/* disk title */
title text,
/* the type of the artist group, person, orchestra*/
type smallint,
/* the creation date */
created integer
);
CREATE INDEX cddb1
sto cercando di installare la versione beta4 di
postgresql su windows ma ho un errore quando richiamo il file. Ho già impostato
le variabili d'ambiente ma quando appunto richiamo il file mi dà un errore di
connessione: could not connect to server: Socket error, no description
available
PSQL.EXE: could not connect to server: Socket error, no description available
(0X2740)
Is the server running
on host localhost and accepting TCP/IP connection on port
5432?
Darren,
I’ve downloaded and built the pgreplication (using
spread) on our RH linux system; I have not installed the patch yet. I’ve
configured users and database ‘testing’ on the Postgres db.
However, I can not seem to bring the postmaster up in master mode.
Postmaster –r –X does not s
Jeremy Yoder <[EMAIL PROTECTED]> writes:
> I compiled with zlib 1.2.1 and can't reproduce the error, but that
> probably has nothing to do with it. It looks like there's a sleep right
> before the test that failed. Perhaps it didn't sleep long enough?
Much more likely this indicates that the s
Scott Yeadon <[EMAIL PROTECTED]> writes:
> The log output postgres returned is as follows:
> FATAL: the database system is shutting down
Sounds to me like something told the postmaster to shut down (sent it a
SIGTERM signal, in other words). If you are certain you did not do this
manually, look
"Tanya Mamedalin" <[EMAIL PROTECTED]> writes:
> Possible ways to reproduce the error: Run a multipart query similar to:
> SELECT DISTINCT o.outage_id, o.machine, o.service, o.level, o.comments,
> o2.time, e.num
>FROM outages o, outages o2, escalation e
>WHERE o.outage_id='31009'
>
bs <[EMAIL PROTECTED]> writes:
> I have upgraded to version 7.4.0 (compiling the software and migrating
> the database using dump/restore)
> Now the following plan is produced
> Hash Join (cost=17.08..42.15 rows=7 width=74)
>Hash Cond: ("outer".id = "inner".entry)
>-> Seq Scan on cddb
Yes, this is an FAQ. Use EXECUTE.
---
PostgreSQL Bugs List wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1064
> Logged by: Sergey
>
> Email address: [EMAIL PROTECTED]
>
> Pos
We have an FAQ for this:
4.26) Why can't I reliably create/drop
temporary tables in PL/PgSQL functions?
It says temporary tables, but it is valid for real tables too when you
creating/dropping them in the function.
"Tanya Mamedalin" <[EMAIL PROTECTED]> writes:
> I was running the same Python code with Postgres 7.2.3 and psycopg 1.0.9
> with no errors. As soon as I upgraded to Postgres 7.4-0.3 and pyscopg 1.1.6
> I started getting errors when trying to execute a certain query.
BTW, this might be the same bug
17 matches
Mail list logo
