Hi Y'all.
I have been getting the dreaded "unexpected EOF on client
connection" in my system logs, but the surprising thing is that
it comes from psql (I think). I am executing psql
via a 'system' system call, and about 1 time out of 20 I get
the "unexpected EOF" message. Unfortunately, this
also
hello,
I just had a DB crash when interrupting manually a drop table operation,
and when interrupting manually (using kill) a vacuumdb operation. Is it
normal, or is it a bug?
thanks a lot,
STan
---
Stanislas Pinte
Software engineer - Tr
Stanislas Pinte wrote:
>
> hello,
>
> I just had a DB crash when interrupting manually a drop table operation,
> and when interrupting manually (using kill) a vacuumdb operation. Is it
> normal, or is it a bug?
>
What does the DB crash mean ?
Regards,
Hiroshi Inoue
IIRC, index functions can take multiple arguments, it's just that
they cannot take constants. I think the values must all be columns
of the tables. So for example, this should work (seems to at
least create on 7.1beta3):
create table aaa (a int, b int, c text);
create index blah on aaa(substr(c,
Scott Marlowe ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
cannot index functions with multiple arguments
Long Description
Postgresql version: 7.1beta2
OS: RedHat Linux 7.0
Postgresql allows indexing of functions applied to