On Sun, Jun 8, 2014 at 09:33:04AM +1200, Gavin Flower wrote:
I know that I first look at the docs seldom look at the Wiki - in
fact it was only recently that I became aware of the Wiki, and it is
still not the first thing I think of when I want to know something,
and I often forget it
David G Johnston david.g.johns...@gmail.com wrote:
For example, even a read only transaction at this level may see a
control record updated to show that a batch has been completed but
not see one of the detail records which is logically part of the
batch because it read an earlier revision
On 08/06/14 05:03, Kevin Grittner wrote:
[...]
I found it hard to decide how far to go in the docs versus the Wiki
page. Any suggestions or suggested patches welcome.
[...]
I know this is subjective, but that seems to me a little too much in
an academic style for the docs. In the Wiki page
Feel free to flame me if I should be posting this elsewhere, but after reading
the submitting a patch guide, it appears I should ask for guidance here.
I was reading the Postgres MVCC documentation today (which is generally
fantastic BTW), and am slightly confused by a single sentence example,
On 05/27/2014 10:12 PM, Evan Jones wrote:
I was reading the Postgres MVCC documentation today (which is
generally fantastic BTW), and am slightly confused by a single
sentence example, describing possible read-only snapshot isolation
anomalies. I would like to submit a patch to clarify this
Oh yeah, I shared an office with Dan so I should have thought to check their
paper. Oops. Thanks for the suggestion; I'll try to summarize this into
something that is similar to the Read Committed and Serializable mode examples.
It may take me a week or two to find the time, but thanks for the
Heikki Linnakangas-6 wrote
On 05/27/2014 10:12 PM, Evan Jones wrote:
I was reading the Postgres MVCC documentation today (which is
generally fantastic BTW), and am slightly confused by a single
sentence example, describing possible read-only snapshot isolation
anomalies. I would like to
