| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGFIX] amcanbackward is not checked before building backward index paths |
| Date: | 2018-05-16 13:54:31 |
| Message-ID: | 908.1526478871@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> On Wed, May 16, 2018 at 1:41 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Perhaps there is a case for adding an additional flag to allow specifying
>> "I can't support ORDER BY DESC", but I'm not in a big hurry to do so.
>> I think there would be more changes than this needed to handle such a
>> restriction, anyway.
> OK, got it. We'll probably propose a patch implementing that to the
> next commitfest.
If you do, it wouldn't be a bad idea to try to clarify the existing
code and docs around this point. I'm thinking that amcanbackward is
misleadingly named; maybe we should rename it as part of the change?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2018-05-16 14:06:55 | Re: index scan over composite type |
| Previous Message | Hubert Zhang | 2018-05-16 13:50:24 | Re: Considering signal handling in plpython again |