On Tue, Jun 12, 2001 at 09:06:17PM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > coalesce in execute crashes backend
>
> Try the attached patch to 7.1.2. I see Jan's already fixed this in
> current sources, but not in the 7.1 branch ...
>
Excellent!! That fixed it.
Will this fix then
[EMAIL PROTECTED] writes:
> coalesce in execute crashes backend
Try the attached patch to 7.1.2. I see Jan's already fixed this in
current sources, but not in the 7.1 branch ...
regards, tom lane
*** src/pl/plpgsql/src/pl_exec.c.orig Mon May 7 21:02:03 2001
--- src/p
Sorry that I have no answer but I just loved this line...
> Even if I type it slowly and hit the keys very hard.
--Rainer
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Rafal Boni ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
failed connect from ecpg destroys evidence of failure
Long Description
PostgreSQL version 7.1.2, built from source, on Linux (RH 6.2)
If a CONNECT form ecpg fails, the
Vinod Kurup ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
coalesce in execute crashes backend
Long Description
When I use a coalesce statement to calculate an expression that is part of a dynamic
query, it crashes the backen
great, thank you much. i wanted to know, in part, that i hadn't missed
something. i'm going to use the same serial and hope that values aren't
entered in the Id field (i won't provide a way to do it in my client app,
so it should be safe enough). but the extra security is valuable to me,
to cov
Hi,
first: please excuse my terrible english ... i'm from germany :-)
second: I don't know, whether this is a bug nor whats wrong.
Sometimes we got the following error-message:
PostgresSQL query failed: FATAL 1: Socket command type 2 unknown
pqReadData() -- backend closed the channel unexpectedl
I've got a system with a few files that have lots of inserts
and then a batch of deletes every hour if there are too many
rows in the table.
There is an index on the table.
The index file seems to grow (slowly) without bound, and vacuum doesn't
reclaim the space. Even if I type it slowly and