On Mon, Jul 24, 2017 at 6:16 PM, Tom Lane wrote:
> Mat Arye writes:
> > On Mon, Jul 24, 2017 at 1:38 PM, Tom Lane wrote:
> >> I'm not really sure why planner hooks would have anything to do with
> your
> >> exposed SQL API?
>
> > Sorry what I meant w
(adding -hackers back into thread, got dropped by my email client, sorry)
On Mon, Jul 24, 2017 at 1:38 PM, Tom Lane wrote:
> Mat Arye writes:
> > I tried looking in the contrib modules and didn't find many with lots of
> > planner hook usage.
>
> I'm not real
On Sat, Jul 22, 2017 at 10:50 AM, Robert Haas wrote:
> On Fri, Jul 21, 2017 at 4:17 PM, Mat Arye wrote:
> > (I
> > want to avoid having to keep backwards-compatibility for all functions in
> > future shared-libraries).
>
> Are you sure that's a good idea?
No :
m if upgrading to an intermediate (not
latest) version.
Solution: MODULE_PATHNAME cannot be used, and we should build our own
templating/makefile infrastructure to link files to the right-versioned
shared library in the CREATE FUNCTION definition.
Thanks a lot in advance,
Mat Arye
http://www.timescale.com/
On Sun, May 7, 2017 at 3:48 PM, Tom Lane wrote:
> Mat Arye writes:
> > This is in arrayfuncs.c:5022 (postgre 9.6.2)
>
> > /*
> > * Ensure pass-by-ref stuff is copied into mcontext; and detoast it too if
> > * it's varlena. (You might think that detoasti
Hi,
I am trying to create a custom aggregate and have run across some puzzling
code while trying to figure out how to implement it.
This is in arrayfuncs.c:5022 (postgre 9.6.2)
/*
* Ensure pass-by-ref stuff is copied into mcontext; and detoast it too if
* it's varlena. (You might think that det
Hi,
I am on a team developing an open-source extension for time-series data
storage in PostgreSQL (https://github.com/timescaledb/timescaledb).
We are trying to extend/hook into the planner so that it understands that
date_trunc('minute', time) has the same ordering as time (or rather that a
sort
