Re: Pipelining executions to postgresql server

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mikko Tiihonen <Mikko(dot)Tiihonen(at)nitorcreations(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Pipelining executions to postgresql server
Date: 2014-11-04 01:10:05
Message-ID: 32086.1415063405@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Mikko Tiihonen <Mikko(dot)Tiihonen(at)nitorcreations(dot)com> writes:
> I do not quite grasp why not sending Sync is so important. My proof of concept setup was for queries with autocommit enabled.

The point is that that will be very, very much harder to use than doing
it the other way. It's fairly easy to reason about the results of
single-transaction pipelined queries: they're all or nothing. If you
fire off queries that are going to autocommit independently, then you
have to worry about all combinations of success/failure, and you won't
have the opportunity to adjust on the fly. It'll be very much like
sending a fixed (predetermined) SQL script to the server using a scripting
language that lacks any conditionals. People certainly do use fixed
scripts sometimes, but they usually find out they want them wrapped into
single transactions, because otherwise they're left with a horrible mess
if the script goes off the rails at all.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2014-11-04 01:24:04 Re: pg_multixact not getting truncated
Previous Message Alvaro Herrera 2014-11-04 01:06:57 Re: pg_multixact not getting truncated

Browse pgsql-jdbc by date

  From Date Subject
Next Message Craig Ringer 2014-11-04 01:56:17 Re: [HACKERS] Pipelining executions to postgresql server
Previous Message Mikko Tiihonen 2014-11-03 23:56:22 Re: Pipelining executions to postgresql server