Hello,
I've got a problem with the 7.0.2 version of Postgres.
In production, the postmaster stops frequently alone
(about one time per hour).
Error message:
postmaster: ServerLoop; select failed; No child
processes
And we have to restart it each hour.
Any idea ?
Thanks for your help
Jérôme Cro
Juri Memmert ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
No Postgres Bug! Heavy downloading problems...
Long Description
Greetings and sorry for wasting your time with a bug report on this...
but from most available mirrors
=?iso-8859-1?q?jerome=20crouigneau?= <[EMAIL PROTECTED]> writes:
> I've got a problem with the 7.0.2 version of Postgres.
> In production, the postmaster stops frequently alone
> (about one time per hour).
> Error message:
> postmaster: ServerLoop; select failed; No child
> processes
This is a kn
[EMAIL PROTECTED] writes:
> but from most available mirrors, I have tried to download the latest version.
> After a maximum of 6% the download stalls on all of them. and even in
> that time, the download is terribly slow (1 byte per second is not
> unusual)
Hmm. Where are you trying to download
On Wed, Feb 28, 2001 at 10:08:50AM -0500, [EMAIL PROTECTED] wrote:
> Juri Memmert ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> No Postgres Bug! Heavy downloading problems...
>
> Long Description
> Greetings and sorry
Mark Reibert ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
RPM postinstall script fails in postgresql-server-7.0.3-2.i386.rpm
Long Description
Installing postgresql-server-7.0.3-2.i386.rpm on a Red Hat 6.2 box resulted in the
[EMAIL PROTECTED] wrote:
>
> Mark Reibert ([EMAIL PROTECTED]) reports a bug with a severity of 3
> [root]# rpm -qp --scripts postgresql-server-7.0.3-2.i386.rpm
> postinstall script (through /sbin/ldconfig):
Thanks for the bug report -- the 7.1 beta and the latest 7.0.3 (21?)
RPM's have this fix
Justin Clift ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Wrong output for 7.0.3 from NULL fields in CASE statement
Long Description
I am getting output that doesn't make sense from a simple SQL statement. I am
expecting t
[EMAIL PROTECTED] writes:
> foobar=# select text(CASE WHEN (cashback = NULL or cashback = 0) THEN '0' ELSE
>cashback END) from transaction_payments where idnum = 139 and payment_type = 6;
> text
> ---
> 1.01855797968803e-312
> (1 row)
Try not quoting the '0'. For r
Sorry, forgot to put the -request on the end of the username in the
email address.
+ Justin Clift
> I am getting output that doesn't make sense from a simple SQL statement.
> I am expecting to get a '0'::text returned by this statement, but
> instead I'm getting very, very small numbers, or other weird things.
> It's a catch for NULL values and isn't interpreting them correctly when
> it gets
11 matches
Mail list logo