From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: searching in array function - array_position |
Date: | 2015-01-21 06:31:12 |
Message-ID: | CAFj8pRAt-q8ibcPwDQLhAE8-MPL-HtESacBL-EMzhSNcM0LF2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-01-20 21:32 GMT+01:00 Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>:
> On 1/20/15 11:12 AM, Pavel Stehule wrote:
>
>> I am sending updated version - it allow third optional argument that
>> specify where searching should to start. With it is possible repeatably
>> call this function.
>>
>
> What happened to returning an array of offsets? I think that would be both
> easier to use than this version as well as performing better.
>
I have still thinking about this idea. It needs a different function and I
didn't start with this.
Implementation a optional start parameter to array_offset is cheap - and I
am thinking so it can be useful for some use cases.
>
> I see you dropped multi-dimension support, but I think that's fine.
It can be implemented later. There is no any barriers to later
implementation.
> --
> Jim Nasby, Data Architect, Blue Treble Consulting
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2015-01-21 06:32:44 | Re: Merging postgresql.conf and postgresql.auto.conf |
Previous Message | Amit Kapila | 2015-01-21 06:21:26 | Re: Parallel Seq Scan |