Re: anyelement -> anyrange

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>
Subject: Re: anyelement -> anyrange
Date: 2016-08-19 16:37:35
Message-ID: CADkLM=cR2ccoUtVG4Sguf3YWNzfnBiM8_9otCnxEtbvOocQB7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 19, 2016 at 11:40 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
wrote:

> On 8/18/16 6:02 PM, Corey Huinker wrote:
>
>> I'd be happy to roll your code into the extension, and make it marked
>> more stable.
>>
>
> Yeah, I've been meaning to look at submitting a pull request; hopefully
> will get to it today.
>
>
No rush, I'm on vacation. Though I really do appreciate other eyes on the
code and other people using it.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2016-08-19 17:29:09 Re: Curing plpgsql's memory leaks for statement-lifespan values
Previous Message Konstantin Knizhnik 2016-08-19 16:36:26 Re: Logical decoding restart problems