| From: | Marsh Ray <marsh5143(at)gmail(dot)com> |
|---|---|
| To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Commit visibility guarantees |
| Date: | 2009-05-18 22:52:30 |
| Message-ID: | 2afbdd3f0905181552k21ead6e8r838d703cc7cac14c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 18, 2009 at 5:24 PM, Sam Mason <sam(at)samason(dot)me(dot)uk> wrote:
> Even then it's not useful to class it as real-time; nothing "bad"
> happens if you don't get a response before timeout the user just gets an
> error message. Real-time applies when if you don't get a response the
> plane crashes or a heart stops because the pacemaker hasn't put out a
> signal in time.
Think of a network router: it is neither a pacemaker nor an airplane
but is definitely a real-time system. If it cannot complete its
processing on time, not only is it useless, it may actually bring down
significant numbers of other systems.
- Marsh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marsh Ray | 2009-05-18 22:54:54 | Re: Commit visibility guarantees |
| Previous Message | Howard Cole | 2009-05-18 22:28:47 | Where is tsearch2.sql |