pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ravi Krishna <srkrishna@gmx.com>
To: pgsql-sql@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Does PG support bulk operation in embedded C
Date: Tue, 19 May 2015 19:47:12 -0400
Message-ID: <8A634A74EF65401FBE09169A72984EBB@RaviLaptop> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>

To explain pls refer to this for DB2

http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.apdv.cli.doc/doc/r0002329...

Essentially in one single sql call, we can do
-- Add new rows
-- Update a set of rows where each row is identified by a bookmark
-- Delete a set of rows where each row is identified by a bookmark
-- Fetch a set of rows where each row is identified by a bookmark

This gives tremendous performance benefits as the network round trip is 
avoided for each sql.

I am looking for an equivalent of this in PG and C language.

Thanks.



-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



view thread (9+ messages)  latest in thread

Message-ID: <8A634A74EF65401FBE09169A72984EBB@RaviLaptop>
Permalink:  ../8A634A74EF65401FBE09169A72984EBB@RaviLaptop/
Also on:    postgresql.org/message-id/8A634A74EF65401FBE09169A72984EBB@RaviLaptop

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: srkrishna@gmx.com, pgsql-general@postgresql.org
  Subject: Re: Does PG support bulk operation in embedded C
  In-Reply-To: <8A634A74EF65401FBE09169A72984EBB@RaviLaptop>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox