Re: Accelerating aggregates

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Accelerating aggregates
Date: 2004-06-14 20:48:50
Message-ID: 87y8mp987h.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Steve Atkins <steve(at)blighty(dot)com> writes:

> On Fri, Jun 11, 2004 at 12:17:57PM -0400, Greg Stark wrote:
>
> > no, read committed would see any other updates that have been committed since
> > the start of your transaction.
>
> Uhm... only updates within the current transaction.

No, "read committed" refers to being able to read any updates that are
committed, even if they were committed after the start of your transaction:

For example:

db=> begin;
BEGIN

db=> begin;
BEGIN

db=> insert into test values (1);
INSERT 6725927 1
db=> select * from test;
a
---
1
(1 row)

db=> select * from test;
a
---
(0 rows)

db=> commit;
COMMIT

db=> select * from test;
a
---
1
(1 row)

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Garamond 2004-06-14 21:44:02 "An old version of the database format was found."
Previous Message Tom Lane 2004-06-14 20:18:24 Spinlock assembly cleanup