| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Andrey Klychkov <aaklychkov(at)mail(dot)ru>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Re[2]: |
| Date: | 2020-05-27 12:18:43 |
| Message-ID: | 5816.1590581923@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Tue, May 26, 2020 at 10:50:19AM -0400, Tom Lane wrote:
>> ... Perhaps the
>> documentation isn't clear enough about that, but I don't see a
>> bug there.
> There is a paragraph about the handling of invalid indexes on the
> reindex page:
Yeah, but the OP is invoking this via reindexdb. Do we need to have
anything about it on the reindexdb page?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Lucas | 2020-05-27 15:23:06 | Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation |
| Previous Message | Tom Lane | 2020-05-27 12:16:55 | Re: BUG #16465: Inconsistent results from comparison of row value expressions |