From: | Robert Hodges <robert(dot)hodges(at)continuent(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot standby, overflowed snapshots, testing |
Date: | 2009-11-14 16:43:59 |
Message-ID: | C7241E4F.1786E%robert.hodges@continuent.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Simon and Heikki,
I can help set up automated basic tests for hot standby using 1+1 setups on
Amazon. I¹m already working on tests for warm standby for our commercial
Tungsten implementation and need to solve the problem of creating tests that
adapt flexibly across different replication mechanisms.
It would be nice to add a list of test cases to the write-up on the Hot
Standby wiki (http://wiki.postgresql.org/wiki/Hot_Standby) I would be
happy to help with that effort.
Cheers, Robert
On 11/13/09 1:43 PM PST, "Simon Riggs" <simon(at)2ndQuadrant(dot)com> wrote:
> On Fri, 2009-11-13 at 22:19 +0200, Heikki Linnakangas wrote:
>
>> I got the impression earlier that you had some test environment set up
>> to test hot standby. Can you share any details of what test cases
>> you've run?
>
> Fair question. The Sep 15 submission happened too quickly for us to
> mobilise testers, so the final submission was submitted with only manual
> testing by me. Many last minute major bug fixes meant that the code was
> much less tested than I would have hoped - you found some of those while
> I lay exhausted from the efforts to hit a superimposed and unrealistic
> deadline. I expected us to kick in to fix those but it never happened
> and that was why I was keen to withdraw the patch about a week later.
>
> You've been kicking hell out of it for a while now, rightly so, so I've
> left it a while before commencing another set of changes and more
> testing to follow.
>
> It takes time, and money, to mobilise qualified testers, so that should
> begin again shortly.
>
> I agreed with you at PGday that we shouldn't expect a quick commit.
> There are good reasons for that, but still no panic in my mind about
> skipping this release.
>
> --
> Simon Riggs www.2ndQuadrant.com
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2009-11-14 16:45:51 | Re: operator exclusion constraints |
Previous Message | Tom Lane | 2009-11-14 16:40:18 | Re: Inspection of row types in pl/pgsql and pl/sql |