Re: [HACKERS] Incorrect cursor behaviour with gist index

2008-10-20 Thread Martin Schäfer
> Okay. I'll go fix the core code, and you can take out > whatever you want in GiST/GIN. Which PostgreSQL versions will contain the fix? Regards, Martin Schaefer -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.

Re: [HACKERS] Incorrect cursor behaviour with gist index

2008-10-17 Thread Tom Lane
Teodor Sigaev <[EMAIL PROTECTED]> writes: >> to use it when the AM can't guarantee to return the same sequence of >> tuples after backing up. So I think it would be sufficient to have >> gistmarkpos et al throw error if called. > Why not to remove gistrestrpos/gistmarkpos/ginrestrpos/ginmarkpos f

Re: [HACKERS] Incorrect cursor behaviour with gist index

2008-10-17 Thread Teodor Sigaev
to use it when the AM can't guarantee to return the same sequence of tuples after backing up. So I think it would be sufficient to have gistmarkpos et al throw error if called. Why not to remove gistrestrpos/gistmarkpos/ginrestrpos/ginmarkpos from pg_am table? -- Teodor Sigaev

Re: [HACKERS] Incorrect cursor behaviour with gist index

2008-10-17 Thread Tom Lane
Teodor Sigaev <[EMAIL PROTECTED]> writes: >> Seems like a lotta work for a partial solution :-(. Probably the path >> of least resistance is to teach the planner that only some index AMs can >> do backwards scan. That would result in a Materialize buffer getting >> placed in front of the query if

Re: [HACKERS] Incorrect cursor behaviour with gist index

2008-10-17 Thread Teodor Sigaev
Seems like a lotta work for a partial solution :-(. Probably the path of least resistance is to teach the planner that only some index AMs can do backwards scan. That would result in a Materialize buffer getting placed in front of the query if the user demanded scroll capability, but it would co

Re: [HACKERS] Incorrect cursor behaviour with gist index

2008-10-17 Thread Tom Lane
Teodor Sigaev <[EMAIL PROTECTED]> writes: > I'm back, sorry for a long absence. > About this bug: http://archives.postgresql.org/pgsql-bugs/2008-09/msg00086.php > Unfortunately, GiST index doesn't work with change direction of scan. I.e. it > can't move forward then move backward and this behavio

[HACKERS] Incorrect cursor behaviour with gist index

2008-10-17 Thread Teodor Sigaev
I'm back, sorry for a long absence. About this bug: http://archives.postgresql.org/pgsql-bugs/2008-09/msg00086.php Unfortunately, GiST index doesn't work with change direction of scan. I.e. it can't move forward then move backward and this behaviour was from the beginning. I think it's fixabl