pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Markus Wanner <markus@bluegap.ch>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: MARK CALLAGHAN <mdcallag@gmail.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Date: Wed, 23 Mar 2011 13:16:39 +0100
Message-ID: <4D89E4A7.4090900@bluegap.ch> (raw)
In-Reply-To: <AANLkTik0WoT+qwh09EUetgFVZy8zpm1Sc3hspa4ddJjs@mail.gmail.com>
References: <E1PwMns-00047O-UU@gemulon.postgresql.org>
	<1299454125.1696.6138.camel@ebony>
	<4D74896C.5030402@enterprisedb.com>
	<4D74DDFA.70800@dunslane.net>
	<4D74E584.7080409@enterprisedb.com>
	<4D74E9FA.7070202@dunslane.net>
	<AANLkTinkzJ=UrLbThZy2KeQg+SjwYqj2r0mDomMwirB7@mail.gmail.com>
	<4D74F3AE.9000802@dunslane.net>
	<4D74FDEC.5040406@enterprisedb.com>
	<4D74FF15.1070804@dunslane.net>
	<1299513979-sup-1987@alvh.no-ip.org>
	<4D832571.5030808@bluegap.ch>
	<AANLkTi=B+cWE-pQJQM=zoA9=Zr25W7zPPMFvvBe11O4E@mail.gmail.com>
	<1300457958.18619.13780.camel@ebony>
	<4D832B4D020000250003BA98@gw.wicourts.gov>
	<4D837EA2.2070205@enterprisedb.com>
	<1300465171.18619.15193.camel@ebony>
	<4D83B02A.5090105@bluegap.ch>
	<1300476590.18619.18115.camel@ebony>
	<4D83B54C.2030708@bluegap.ch>
	<AANLkTimdn_yVBwsNXn9bnOvDmhxHKyLNBqJYab_Oji4z@mail.gmail.com>
	<AANLkTi=bD6iWZNggors9ooG-ZjXwxy6b=DPMWf160WNO@mail.gmail.com>
	<4D89A0D1.4030601@bluegap.ch>
	<AANLkTik0WoT+qwh09EUetgFVZy8zpm1Sc3hspa4ddJjs@mail.gmail.com>

On 03/23/2011 12:52 PM, Robert Haas wrote:
> Yes.  What this won't do is let you build a big load-balancing network
> (at least not without great caution about what you assume).

This sounds too strong to me.  Session-aware load balancing is pretty
common these days.  It's the default mode of PgBouncer, for example.
Not much caution required there, IMO.  Or what pitfalls did you have in
mind?

> What it
> will do is make it really, really hard to lose committed transactions.
> Both good things, but different.

..you can still get both at the same time.  At least as long as you are
happy with session-aware load balancing.  And who really needs finer
grained balancing?

(Note that no matter how fine-grained you balance, you are still bound
to a (single core of a) single node.  That changes with distributed
querying, and things really start to get interesting there... but we are
far from that, yet).

Regards

Markus



view thread (85+ messages)  latest in thread

Message-ID: <4D89E4A7.4090900@bluegap.ch>
Permalink:  ../4D89E4A7.4090900@bluegap.ch/
Also on:    postgresql.org/message-id/4D89E4A7.4090900@bluegap.ch

 · 

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-hackers@postgresql.org
  Cc: markus@bluegap.ch, robertmhaas@gmail.com, aidan@highrise.ca, simon@2ndquadrant.com, heikki.linnakangas@enterprisedb.com, Kevin.Grittner@wicourts.gov, mdcallag@gmail.com, alvherre@commandprompt.com, andrew@dunslane.net
  Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
  In-Reply-To: <4D89E4A7.4090900@bluegap.ch>

* 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