| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Gurjeet Singh <gurjeet(at)singh(dot)im>, richard(dot)vesely(at)softea(dot)sk, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18016: REINDEX TABLE failure |
| Date: | 2023-07-09 14:18:30 |
| Message-ID: | 1867443.1688912310@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> That should be OK, I assume. However, if this is improved and
> something we want to support in the long-run I guess that a TAP test
> may be appropriate.
I do not see the point of a TAP test. It's not like the code isn't
covered perfectly well.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2023-07-09 15:00:01 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |
| Previous Message | Richard Veselý | 2023-07-09 13:54:35 | RE: BUG #18016: REINDEX TABLE failure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2023-07-09 16:16:26 | Re: BRIN indexes vs. SK_SEARCHARRAY (and preprocessing scan keys) |
| Previous Message | Richard Veselý | 2023-07-09 13:54:35 | RE: BUG #18016: REINDEX TABLE failure |