Re: Faster methods for getting SPI results

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Joe Conway <mail(at)joeconway(dot)com>
Subject: Re: Faster methods for getting SPI results
Date: 2016-12-28 04:32:01
Message-ID: 4d2cea66-c61f-cfb0-7143-d656df12946a@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/27/16 9:10 PM, Craig Ringer wrote:
> On 28 December 2016 at 09:58, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>
>> I've looked at this some more, and ITSM that the only way to do this without
>> some major surgery is to create a new type of Destination specifically for
>> SPI that allows for the execution of an arbitrary C function for each tuple
>> to be sent.
>
> That sounds a lot more sensible than the prior proposals. Callback driven.

Are there other places this would be useful? I'm reluctant to write all
of this just to discover it doesn't help performance at all, but if it's
useful on it's own I can just submit it as a stand-alone patch.
--
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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ideriha, Takeshi 2016-12-28 04:43:38 [WIP] RE: DECLARE STATEMENT setting up a connection in ECPG
Previous Message Thomas Munro 2016-12-28 04:26:40 Re: Some thoughts about multi-server sync rep configurations