Neil Conway wrote:
> There's a minor bug in the ON_ERROR_ROLLBACK code in psql. In HEAD, at
> line 878 the storage pointed to by "results" is released by a PQclear(),
> but is referenced by the PQcmdStatus() calls on lines 898, 899, and 900.
I think this is the fix for HEAD. I'll apply after test
> There's a minor bug in the ON_ERROR_ROLLBACK code in psql. In
> HEAD, at line 878 the storage pointed to by "results" is
> released by a PQclear(), but is referenced by the
> PQcmdStatus() calls on lines 898, 899, and 900.
>
> I'm busy at the moment -- if someone wants to fix this
> (backport
"Wagner Cipriano" <[EMAIL PROTECTED]> writes:
> Error: index "xxx" is not a hash index.
> Always this error happen with me.
You haven't provided enough information to let anyone help you ...
but if you mean that you've got a corrupt index, REINDEXing it
should fix that.
re
There's a minor bug in the ON_ERROR_ROLLBACK code in psql. In HEAD, at
line 878 the storage pointed to by "results" is released by a PQclear(),
but is referenced by the PQcmdStatus() calls on lines 898, 899, and 900.
I'm busy at the moment -- if someone wants to fix this (backport to 8.1
please!),
Alvaro Herrera wrote:
> Russell Francis wrote:
>
>> If a SELECT statement contains a table in it's FROM clause which has 0
>> records in it, the query will not return any results. If a record is added
>> to the table even though it shouldn't modify the results of query, the query
>> will return t
The following bug has been logged online:
Bug reference: 2506
Logged by: Wagner Cipriano
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Linus Suse 10
Description:hash index
Details:
Error: index "xxx" is not a hash index.
Always this erro
