| From: | Anton Ananich <anton(dot)ananich(at)gmail(dot)com> |
|---|---|
| To: | Vick Khera <vivek(at)khera(dot)org> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: GIN Indexes: Extensibility |
| Date: | 2016-07-28 13:57:23 |
| Message-ID: | 21ECC8A0-4087-411F-BAE7-78F83141977A@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Vick, you are right. That’s why I’d wish to add some custom code to MY PostgreSQL instance and set such a sort order, which is optimal for my application.
On Jul 27, 2016, at 17:44, Vick Khera <vivek(at)khera(dot)org> wrote:
> On Wed, Jul 27, 2016 at 3:28 AM, Anton Ananich <anton(dot)ananich(at)gmail(dot)com> 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.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anton Ananich | 2016-07-28 14:03:12 | Re: GIN Indexes: Extensibility |
| Previous Message | Andreas Kretschmer | 2016-07-28 13:54:01 | Re: WAL directory size calculation |