Re: anyelement -> anyrange

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(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 15:40:15
Message-ID: b216de37-bb40-422b-b98a-3541b1397c6c@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-19 15:42:44 Re: Curing plpgsql's memory leaks for statement-lifespan values
Previous Message Jim Nasby 2016-08-19 15:38:50 Re: [PATCH] add option to pg_dumpall to exclude tables from the dump