Markus Bertheau <[EMAIL PROTECTED]> writes:
> I looked and found several postgres processes with parent process init
> and *no* postmaster process.
It looks to me like your postmaster crashed because there were no free
file descriptors left in the system:
FATAL 1: ReleaseLruFile: No open files
Good day,
cenes=> select version();
version
---
PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.95.2
(1 row)
(I know it is old, update is in the queue)
The following hap
[EMAIL PROTECTED] writes:
> When I try to write an UPDATE where I include a WHERE-clause like:
> [WHERE something='{"a","b","c"}], where something is a character[], i get
> the errormessage:[Unable to identify an operator = for types '_bpchar and
> 'unknown' You will have to retype this query usin
On Fri, 14 Dec 2001 [EMAIL PROTECTED] wrote:
> Eugene Fokin ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> Unexpected DeadLock on REFERENCES
>
> Long Description
> DeadLock happens when we're trying to concurrent updat
On Thursday 13 December 2001 05:47 pm, Roger wrote:
> I recently installing Red Hat 7.2. One of RPM were your PostgreSql. I thing
> that there is a bug in the instalallation. Packet is installed correctlt
> with no error messages. When I try to init server by (etc/init.d/postgresql
> start) the Li
When I try to write an UPDATE where I include a WHERE-clause like:
[WHERE something='{"a","b","c"}], where something is a character[], i get
the errormessage:[Unable to identify an operator = for types '_bpchar and
'unknown' You will have to retype this query using an explicit cast]
The above sta
POSTGRESQL BUG REPORT TEMPLATE
Your name : Andrew Pimlott
Your email address : [EMAIL P
Hi!
I recently installing Red Hat 7.2. One of RPM were
your PostgreSql. I thing that there is a bug in the instalallation. Packet is
installed correctlt with no error messages. When I try to init server by
(etc/init.d/postgresql start) the Linux says all is OK. But when I make a port
Scan
Eugene Fokin ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Unexpected DeadLock on REFERENCES
Long Description
DeadLock happens when we're trying to concurrent update different
tables which chained with one table through REFER
Holubniak Piotr ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Backend crasches
Long Description
My system is running on Pentium II 350 with 128 MB memory, WD-SCSI
linux Mandrake 6.0, kernel 2.2.9-27mdk, glibc 1.2.3
Sending
10 matches
Mail list logo