I've also come across this in 7.4. You could also use:
SELECT NULL AS Test
UNION ALL SELECT NULL::int
UNION ALL SELECT 0
Dirk
Tom Lane wrote:
"" <[EMAIL PROTECTED]> writes:
The following query should not raise an error ("ERROR: UNION types text and
integer cannot be matched"):
SELECT
Tom Lane writes:
> Dirk Lutzebaeck <[EMAIL PROTECTED]> writes:
> > Hi, I have the follow problem when vacuum'ing on 7.1.3:
> > ERROR: cannot find attribute 1 of relation docmatchsel
> > Then I tried to reindex the table in standalone mode which gives:
> &
Hi, I have the follow problem when vacuum'ing on 7.1.3:
db1=# vacuum;
ERROR: cannot find attribute 1 of relation docmatchsel
I cannot drop the table either and the system does not seem do know
the columns:
db1=# \d docmatchsel
Table "docmatchsel
Attribute | Type | Modifier
---+--
Stephan Szabo writes:
>
> Unless I'm horribly misreading the spec, this is correct.
> ORDER BY is used in reference to cursor definitions and
> direct select statements, but is not part of query expressions
> which is what the INSERT INTO references.
>
> ::=
> I
Tom Lane writes:
> Dirk Lutzebaeck <[EMAIL PROTECTED]> writes:
> > It may be that there is some kernel corruption appearing here. I'm
> > using kernel nfs on Linux 2.2.10 with a Solaris8 i86pc client. I saw
> > some weird NFS error messages on the Linux syst
Tom Lane writes:
> Dirk Lutzebaeck <[EMAIL PROTECTED]> writes:
> > I observe occasionaly crashes on 7.0.3 under medium load:
>
> > Backend message type 0x49 arrived while idle
> > Backend message type 0x44 arrived while idle
> > Backend message typ
Hello,
I observe occasionaly crashes on 7.0.3 under medium load:
Backend message type 0x49 arrived while idle
Backend message type 0x44 arrived while idle
Backend message type 0x54 arrived while idle
I recently upgraded from 7.0.2 to 7.0.3 on RH6.0, Linux 2.2.10 and I
haven't observed these m
Dirk Lutzebaeck writes:
> ERROR: btree: index item size 3048 exceeds maximum 2717
>
> This is on 7.0.2 while doing an INSERT. The INSERT aborts and returns
> this error. It just occurred now for the first time and now everytime.
> There are several indexes defined on this
ERROR: btree: index item size 3048 exceeds maximum 2717
This is on 7.0.2 while doing an INSERT. The INSERT aborts and returns
this error. It just occurred now for the first time and now everytime.
There are several indexes defined on this table. Should I rebuild
them all?
What is this?
Regar
Bruce Momjian writes:
> This is terrible. I can't imagine how people use this without terrible
> problems. Why don't we get more bug reports about this?
Maybe this relates to this too:
$ pg_dump cs1 -o > /tmp/x.dump
parseNumericArray: bogus number
pg_dump aborts then. This is on 7.0 on Lin
10 matches
Mail list logo
