Re: [BUGFIX] amcanbackward is not checked before building backwardindex paths
| От | David G. Johnston |
|---|---|
| Тема | Re: [BUGFIX] amcanbackward is not checked before building backwardindex paths |
| Дата | |
| Msg-id | CAKFQuwbjw-fcbMBbOER_cg+TpUtp08fyJDmS2xFp3O_oQW+q4g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [BUGFIX] amcanbackward is not checked before building backward index paths (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [BUGFIX] amcanbackward is not checked before building backward index paths
|
| Список | pgsql-hackers |
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> I'll fix the docs accordingly. I'm referring specifically to this bit:
> https://www.postgresql.org/docs/current/static/functions- info.html#FUNCTIONS-INFO- INDEX-PROPS
> which I think should say "Can the scan direction be changed in
> mid-scan?" in place of the current text (unless anyone has better
> wording?)
Maybe "Can the scan direction be reversed in mid-scan?". I'm not
absolutely sure that that's better ...
A cursory read might conclude that "reversing" can only happen once while they will likely understand that "changing" can happen multiple times. This is minor point - the two are effectively the same.
Maybe: "Supports both FETCH FORWARD and FETCH BACKWARD during the same scan"
Or:
"Supports SCROLL(able) WITHOUT HOLD cursors"
David J.
В списке pgsql-hackers по дате отправления: