Re: GIN Indexes: Extensibility
От
Paul Jungwirth
Тема
Re: GIN Indexes: Extensibility
Дата
Msg-id
5ce6efd7-c6dc-2dfd-bc37-c797ad6c9d46@illuminatedcomputing.com
Ответ на
Re: GIN Indexes: Extensibility (Vick Khera)
Список
Дерево обсуждения
GIN Indexes: Extensibility Anton Ananich <anton.ananich@gmail.com>
Re: GIN Indexes: Extensibility Vick Khera <vivek@khera.org>
Re: GIN Indexes: Extensibility Anton Ananich <anton.ananich@gmail.com>
Re: GIN Indexes: Extensibility Paul Jungwirth <pj@illuminatedcomputing.com>
Re: GIN Indexes: Extensibility Anton Ananich <anton.ananich@gmail.com>
On 07/27/2016 07:44 AM, Vick Khera wrote:
> On Wed, Jul 27, 2016 at 3:28 AM, Anton Ananich wrote:
>> In my situation this order is invalid. Obviously, year 2016 should go after
>> 2014, like that:
>
> I think you expect JSONB to sort differently than it does. I cannot
> imagine what a "natural" ordering of arbitrary JSON objects is.
FWIW, Postgres arrays do sort in the way he's expecting:
paul=# create table t (id integer, v integer[]);
CREATE TABLE
paul=# insert into t values (1, array[2014]), (2, array[2014, 1]), (3,
array[2016]);
INSERT 0 3
paul=# select * from t order by v;
id | v
----+----------
1 | {2014}
2 | {2014,1}
3 | {2016}
(3 rows)
So maybe convert to an array before sorting?
Paul
В списке pgsql-general по дате отправления