-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Heikki Linnakangas kirjoitti:
> Jukka Holappa wrote:
>> Currently it has some problem with another index for sure as it says:
>> 'ERROR: could not find left sibling in "next_indexing_key"' and when
>> trying to recreate the url table index that wa
Jukka Holappa wrote:
> Currently it has some problem with another index for sure as it says:
> 'ERROR: could not find left sibling in "next_indexing_key"' and when
> trying to recreate the url table index that was used in the problematic
> query I reported about, I had some errors like:
>
> NOTICE
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Heikki Linnakangas kirjoitti:
> Jukka Holappa wrote:
>> I can't easily reproduce this problem but it happens in every few hours in
>> my use.
>
> Can you get a core dump and/or a stack trace out of it? I noted that
> you're running Gentoo, so rec
Jukka Holappa wrote:
> I can't easily reproduce this problem but it happens in every few hours in
> my use.
Can you get a core dump and/or a stack trace out of it? I noted that
you're running Gentoo, so recompiling with --enable-debug, if it's not
compiled with it already, shouldn't be a problem :
The following bug has been logged online:
Bug reference: 3595
Logged by: Jukka Holappa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Gentoo Linux
Description:Segmentation fault with a simple select query
Details:
I can't easily reprodu
