[HACKERS] Why does plpython delay composite type resolution? - Mailing list pgsql-hackers

From Jim Nasby
Subject [HACKERS] Why does plpython delay composite type resolution?
Date
Msg-id 40a54474-4e21-9539-9f91-805ce72dfed9@BlueTreble.com
Whole thread Raw
Responses Re: [HACKERS] Why does plpython delay composite type resolution?
List pgsql-hackers
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 is to just pre-allocate those 
strings as appropriate for the calling context, but it's not clear how 
to handle that for input arguments.
-- 
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)



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Logical decoding on standby
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Logical decoding on standby