On 12/21/16 8:39 AM, Tom Lane wrote:
Jim Nasby writes:
On 12/21/16 1:55 AM, Andreas Karlsson wrote:
Does your patch handle "ALTER TYPE name ADD ATTRIBUTE ..."? My immediate
guess would be that it could be a cache invalidation thing.
Won't that only happen at end of transaction?
No.
Jim Nasby writes:
> On 12/21/16 1:55 AM, Andreas Karlsson wrote:
>> Does your patch handle "ALTER TYPE name ADD ATTRIBUTE ..."? My immediate
>> guess would be that it could be a cache invalidation thing.
> Won't that only happen at end of transaction?
No.
BEGIN;
SELECT plpython_
On 12/21/16 1:55 AM, Andreas Karlsson wrote:
On 12/21/2016 04:14 AM, Jim Nasby wrote:
Why do functions that accept composite types delay type resolution until
execution? I have a naive patch that speeds up plpy.execute() by 8% by
caching interred python strings for the dictionary key names (whic
On 12/21/2016 04:14 AM, Jim Nasby wrote:
Why do functions that accept composite types delay type resolution until
execution? I have a naive patch that speeds up plpy.execute() by 8% by
caching interred python strings for the dictionary key names (which are
repeated over and over). The next step i