Re: Parallell Optimizer

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Ants Aasma <ants(at)cybertec(dot)at>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, hannu <hannu(at)2ndquadrant(dot)com>, "Fred&Dani&Pandora&Aquiles" <fred(at)nti(dot)ufop(dot)br>, MIchael <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallell Optimizer
Date: 2013-06-13 08:24:31
Message-ID: CA+U5nM++hkXhxGacndqm15SDK20OcUva6hYy0j_wDYdMmX1DNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 13 June 2013 02:18, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * Ants Aasma (ants(at)cybertec(dot)at) wrote:
>> In a cluster setting you take the CSN value on the master, then before
>> starting execution on a standby you wait until that the standby has
>> replayed enough WAL to reach the CSN point read from the master and
>> you know that after that everything that the snapshot can see is also
>> replayed on the standby.
>
> This does make a lot of sense- but to clarify, this would only be for
> certain isolation levels, right? Or would we implement this for every
> snapshot taken in a read-committed transaction?

That idea is not dependent upon CSNs.

It is an option for us to implement snapshot synchronisation now, we
just haven't done it yet.

I'm currently working on exporting/importing snapshots on standbys,
which is a precursor to that idea.

None of the above is any easier/harder with CSNs, nor would it
delay/accelerate delivery of such features.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2013-06-13 08:39:53 Re: Parallell Optimizer
Previous Message Simon Riggs 2013-06-13 08:17:57 Re: Parallell Optimizer