| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jason Kim <git(at)jasonk(dot)me> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Fix select from wrong table array_op_test |
| Date: | 2021-06-11 16:00:41 |
| Message-ID: | 388609f1-fbd9-05b3-801c-513256b5903e@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/06/2021 18:31, Tom Lane wrote:
> Jason Kim <git(at)jasonk(dot)me> writes:
>> In the middle of GIN index testing, there are some selects that are on
>> a different table array_op_test that doesn't even have an index. They
>> probably were supposed to be selects to table array_index_op_test like
>> the other ones around the area.
>
> I think it's probably intentional, else why have two tables at all?
> I suppose the point of these test cases is to confirm that you get the
> same results with or without use of an index.
We already have these same queries in the 'arrays' test against the
'array_op_test' table, though. It sure looks like a copy-paste error to
me as well.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2021-06-11 16:25:21 | Re: Transactions involving multiple postgres foreign servers, take 2 |
| Previous Message | Tom Lane | 2021-06-11 15:31:15 | Re: [PATCH] Fix select from wrong table array_op_test |