Re: Incorrect cursor behaviour with gist index - Mailing list pgsql-hackers

From Teodor Sigaev
Subject Re: Incorrect cursor behaviour with gist index
Date
Msg-id 48F8FDC8.1070705@sigaev.ru
Whole thread Raw
In response to Re: Incorrect cursor behaviour with gist index  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Incorrect cursor behaviour with gist index
List pgsql-hackers
> 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                                   E-mail: teodor@sigaev.ru
  WWW: http://www.sigaev.ru/
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Incorrect cursor behaviour with gist index
Next
From: Tom Lane
Date:
Subject: Re: Incorrect cursor behaviour with gist index