| From: | Daniel Farina <daniel(at)heroku(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | simon(at)2ndquadrant(dot)com, heikki(dot)linnakangas(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Sync Rep v17 |
| Date: | 2011-02-21 22:55:38 |
| Message-ID: | AANLkTi=_dq-Y_R+n4sbB599XLqT7Pa4713aPecxDF+zA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 21, 2011 at 4:35 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>> Well, good news all round.
Hello on this thread,
I'm taking a look at replication timeout with non-blocking which would
be "nice" but not required for this patch, in my understanding. But
before that, we're going to put this patch through some exercise via
pgbench to determine two things:
* How much performance is impacted
* Does it crash?
As it will be somewhat hard to prove the durability guarantees of
commit without special heroics, unless someone can suggest a
mechanism. Expect some results Real Soon.
--
fdr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-02-21 23:11:41 | validating foreign tables |
| Previous Message | Kevin Grittner | 2011-02-21 21:39:26 | Re: Snapshot synchronization, again... |