Hi, Madison,

Does it mean, that you are going to implement MVCC
(multi-version concurrency control) in IDS?

What type of MVCC are you going to implement:
Postgress/MySQL-InnoDB type (when UPDATE is internally
converted by the database server into INSERT, and all
versions of a record are kept in a table)
or Oracle-style (when old versions of a row are only
available temporarily in RBS, roll-back segments)?

Is it possible to continue working with non-versioned
tables? many applications rely on 'select' locks,
it makes sense to preserve select locks for compatibility...


-Alexey


> -----Original Message-----
> From: informix-list-bounces@iiug.org
[mailto:informix-list-bounces@iiug.org]
> On Behalf Of Madison Pruet
>
> There is a bit of mis-communication with this. What we are doing is
> implementing a form of row versioning which will enable a select to
view
> the currently committed row rather than blocking on the row when it
is
> in the process of being updated and is locked.
>

Alexey Sonkin wrote:
> Hi, Madison,
>
> Does it mean, that you are going to implement MVCC
> (multi-version concurrency control) in IDS?

Come to the conference for details...

M.P.

>
> What type of MVCC are you going to implement:
> Postgress/MySQL-InnoDB type (when UPDATE is internally
> converted by the database server into INSERT, and all
> versions of a record are kept in a table)
> or Oracle-style (when old versions of a row are only
> available temporarily in RBS, roll-back segments)?
>
> Is it possible to continue working with non-versioned
> tables? many applications rely on 'select' locks,
> it makes sense to preserve select locks for compatibility...
>
>
> -Alexey
>
>
>> -----Original Message-----
>> From: informix-list-bounces@iiug.org
> [mailto:informix-list-bounces@iiug.org]
>> On Behalf Of Madison Pruet
>>
>> There is a bit of mis-communication with this. What we are doing is
>> implementing a form of row versioning which will enable a select to
> view
>> the currently committed row rather than blocking on the row when it
> is
>> in the process of being updated and is locked.
>>
>
>