| From: | Greg Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "<Markus Wanner" <markus(at)bluegap(dot)ch>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: User-facing aspects of serializable transactions |
| Date: | 2009-06-01 20:08:08 |
| Message-ID: | 4136ffa0906011308u1a285672y2605b655e5666ad6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 1, 2009 at 8:55 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>
> Whoa! I just noticed this phrase on a re-read. I think there might
> be some misunderstanding here.
>
> You can be sure you've written your transaction safely just as soon as
> your COMMIT returns without error.
I think we have different definitions of "safely". You only know that
you got away with it *this time* when the commit returns without
error.
I'm concerned with whether you can be sure that the 999th time you run
it the database won't randomly decide to declare a serialization
failure for reasons you couldn't predict were possible.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-06-01 20:08:16 | Re: It's June 1; do you know where your release is? |
| Previous Message | Robert Haas | 2009-06-01 20:03:12 | Re: list_head naming conflict gcc 4.2/perl/solaris |