On Mon, 2009-05-18 at 18:44 -0500, Marsh Ray wrote:
> This is a connection kept open for extended periods, and used
> mutithreadedly for selects only.
I have some code that will allow you to reuse snapshots from one session
to another, which could help your multiple threads see a consistent vie
Marsh Ray wrote:
>>> The central question: So if I successfully commit an update
>>> transaction on one connection, then instantaneously issue a select on
>>> another previously-opened connection, under what circumstances am I
>>> guaranteed that the select will see the effects of the update?
>>
>>
Marsh Ray escribió:
> On Mon, May 18, 2009 at 6:20 PM, Tom Lane wrote:
> > Marsh Ray writes:
> >> The central question: So if I successfully commit an update
> >> transaction on one connection, then instantaneously issue a select on
> >> another previously-opened connection, under what circumstan
On Mon, May 18, 2009 at 6:20 PM, Tom Lane wrote:
> Marsh Ray writes:
>> The central question: So if I successfully commit an update
>> transaction on one connection, then instantaneously issue a select on
>> another previously-opened connection, under what circumstances am I
>> guaranteed that th
Marsh Ray writes:
> The central question: So if I successfully commit an update
> transaction on one connection, then instantaneously issue a select on
> another previously-opened connection, under what circumstances am I
> guaranteed that the select will see the effects of the update?
If the sel
On Mon, May 18, 2009 at 5:14 PM, Sam Mason wrote:
> On Mon, May 18, 2009 at 04:38:36PM -0500, Marsh Ray wrote:
>> The central question: So if I successfully commit an update
>> transaction on one connection, then instantaneously issue a select on
>> another previously-opened connection, under what
On Mon, May 18, 2009 at 5:24 PM, Sam Mason 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
On Mon, May 18, 2009 at 05:18:06PM -0500, Marsh Ray wrote:
> On Mon, May 18, 2009 at 4:53 PM, Ben Chobot wrote:
> > On Mon, 18 May 2009, Marsh Ray wrote:
> >> Hello Everyone,
> >> I'm looking at an easy real-time application using PostgreSQL.
> > As I understand real-time applications, PostgreSQL
On Mon, May 18, 2009 at 4:53 PM, Ben Chobot wrote:
> On Mon, 18 May 2009, Marsh Ray wrote:
>> Hello Everyone,
>> I'm looking at an easy real-time application using PostgreSQL.
> As I understand real-time applications, PostgreSQL is inherintly unsuited
> for the task. There is absolutely no timing
On Mon, May 18, 2009 at 04:38:36PM -0500, Marsh Ray wrote:
> The central question: So if I successfully commit an update
> transaction on one connection, then instantaneously issue a select on
> another previously-opened connection, under what circumstances am I
> guaranteed that the select will se
Hello Everyone,
I'm looking at an easy real-time application using PostgreSQL.
Looking at the pg docs, I see lots of discussion about cases where
MVCC may reflect different versions of the data to different
connections. For example:
http://www.postgresql.org/docs/8.1/static/mvcc.html
"while quer
11 matches
Mail list logo
