| From: | Robert Hodges <robert(dot)hodges(at)continuent(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot standby, overflowed snapshots, testing |
| Date: | 2009-11-15 23:19:24 |
| Message-ID: | C725CC7C.17AF0%robert.hodges@continuent.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/15/09 2:25 AM PST, "Simon Riggs" <simon(at)2ndQuadrant(dot)com> wrote:
> On Sat, 2009-11-14 at 08:43 -0800, Robert Hodges wrote:
>
>> 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.
>
> I didn't leap immediately to say yes for a couple of reasons.
>
I'm easy on this. We are going to find some hot standby problems no matter
what from our own testing. At least I hope so.
It does sound to me as if there is a class of errors that would be easiest
to find by putting up a long running test that throws a lot of different
queries at the server over time. We have such tests already written in our
Bristlecone tools.
Cheers, Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-11-15 23:22:44 | Re: Summary and Plan for Hot Standby |
| Previous Message | Tom Lane | 2009-11-15 22:39:56 | Re: Listen / Notify rewrite |