From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extension support for postgres_fdw |
Date: | 2015-06-22 00:40:31 |
Message-ID: | 5587597F.8060501@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/20/15 12:19 PM, Tom Lane wrote:
> Note that no matter what the details are, something like this is putting
> the onus on the DBA to mark as transmittable only functions that actually
> are safe to transmit, ie they exist*and have identical semantics* on the
> remote. I think that's fine as long as it's clearly documented.
That seems like potentially a lot of extra work. We have the actual
function body/definition for all but C functions, perhaps we could
automatically map calls when the definitions are identical.
I think that could operate safely in addition to manual specification
though, so presumably this could be added later.
> (Presumably, only immutable functions would get transmitted, even if there
> are mutable functions present in a marked extension.)
+1
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-06-22 00:49:40 | Re: pretty bad n_distinct estimate, causing HashAgg OOM on TPC-H |
Previous Message | Jim Nasby | 2015-06-22 00:28:56 | Re: checkpointer continuous flushing |