| From: | Daniel Farina <daniel(at)heroku(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, 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-22 19:45:30 |
| Message-ID: | AANLkTimSfAnAAY_YJ4TLVy7NF19AWHZpZz2qMK4hjBG7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 22, 2011 at 5:04 AM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> Daniel Farina wrote:
>>
>> As it will be somewhat hard to prove the durability guarantees of
>> commit without special heroics, unless someone can suggest a
>> mechanism.
>
> Could you introduce a hack creating deterministic server side crashes in
> order to test this out? The simplest thing that comes to mind is a rule
> like "kick shared memory in the teeth to force a crash after every 100
> commits", then see if #100 shows up as expected. Pick two different small
> numbers for the interval and you could probably put that on both sides to
> simulate all sorts of badness.
I probably could via function, would a kill -9 also be of interest to you?
--
fdr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL - Hans-Jürgen Schönig | 2011-02-22 19:48:47 | WIP: cross column correlation ... |
| Previous Message | Jaime Casanova | 2011-02-22 19:43:29 | Re: Sync Rep v17 |