From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
Cc: | "Jeff Davis" <pgsql(at)j-davis(dot)com>,<pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Serializable implementation |
Date: | 2010-01-08 21:59:16 |
Message-ID: | 4B475654020000250002E0F3@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I think anything you decide about how to invoke the different
> isolation levels will be easy to change later to meet whatever the
> consensus of the community is at that time. I wouldn't spend any
> time or energy on it now. For purposes of your prototype patch,
> using REPEATABLE READ for the current serializable and
> SERIALIZABLE for the new behavior will be plenty good enough.
I think the attached (so far noop) patch covers that. This is "for
the record" for those interested; I'm not looking for review per se,
or commit.
-Kevin
P.S. The git hints worked like a charm, and saved much flailing.
Attachment | Content-Type | Size |
---|---|---|
serializable-001.patch | text/plain | 11.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2010-01-08 21:59:47 | Re: [COMMITTERS] pgsql: Also update ChangerLog file. |
Previous Message | Michael Meskes | 2010-01-08 21:57:36 | Re: pgsql: Also update ChangerLog file. |