Re: Incorrect cursor behaviour with gist index

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Martin Schäfer <Martin(dot)Schaefer(at)cadcorp(dot)com>
Subject: Re: Incorrect cursor behaviour with gist index
Date: 2008-10-17 21:04:08
Message-ID: 48F8FDC8.1070705@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-17 21:21:25 Re: Incorrect cursor behaviour with gist index
Previous Message Tom Lane 2008-10-17 20:51:01 Re: Incorrect cursor behaviour with gist index