Re: [HACKERS] Faster methods for getting SPI results - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Faster methods for getting SPI results
Date
Msg-id 7249067c-82a9-5807-abed-ffd95c812d7c@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Faster methods for getting SPI results  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [HACKERS] Faster methods for getting SPI results  (Jon Nelson <jnelson+pgsql@jamponi.net>)
Re: [HACKERS] Faster methods for getting SPI results  (Jim Nasby <jim.nasby@openscg.com>)
List pgsql-hackers
On 12/20/16 23:14, Jim Nasby wrote:
> I've been looking at the performance of SPI calls within plpython. 
> There's a roughly 1.5x difference from equivalent python code just in 
> pulling data out of the SPI tuplestore. Some of that is due to an 
> inefficiency in how plpython is creating result dictionaries, but fixing 
> that is ultimately a dead-end: if you're dealing with a lot of results 
> in python, you want a tuple of arrays, not an array of tuples.

There is nothing that requires us to materialize the results into an
actual list of actual rows.  We could wrap the SPI_tuptable into a
Python object and implement __getitem__ or __iter__ to emulate sequence
or mapping access.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [HACKERS] Speedup twophase transactions
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Backport of pg_statistics typos fix