Thank you.
On Tue, Jun 28, 2016 at 11:06 PM Oleg Bartunov wrote:
> On Wed, Jun 29, 2016 at 6:17 AM, M Enrique <
> enrique.mailing.li...@gmail.com> wrote:
>
>> What's a good source code entry point to review how this is working for
>> anyarray currently? I am new to the postgres code. I spend som
On Wed, Jun 29, 2016 at 6:17 AM, M Enrique
wrote:
> What's a good source code entry point to review how this is working for
> anyarray currently? I am new to the postgres code. I spend some time
> looking for it but all I found is the following (which I have not been able
> to decipher yet).
>
L
What's a good source code entry point to review how this is working for
anyarray currently? I am new to the postgres code. I spend some time
looking for it but all I found is the following (which I have not been able
to decipher yet).
[image: pasted1]
Thank you,
Enrique
On Tue, Jun 21, 2016 at
Enrique MailingLists writes:
> Currently creating an index on an array of UUID involves defining an
> operator class. I was wondering if this would be a valid request to add as
> part of the uuid-ossp extension? This seems like a reasonable operator to
> support as a default for UUIDs.
This makes
On Tue, Jun 21, 2016 at 11:42 AM, Enrique MailingLists
wrote:
> This would be helpful for people trying to use arrays of UUIDs in cloud
> environments which limit root access.
I have personally seen numerous requests for this from users of Heroku
Postgres. So, I agree that there is a demand for t
Currently creating an index on an array of UUID involves defining an
operator class. I was wondering if this would be a valid request to add as
part of the uuid-ossp extension? This seems like a reasonable operator to
support as a default for UUIDs. Any downsides to adding this as a default?
http:
