[ovs-dev] [PATCH v2] vswitchd: Make Interface's ofport a persistent column.

[Gurucharan Shetty]

>
> This is because we cannot be sure that the commit will be effective.
> The database supports many clients all working concurrently, which means
> that any update we ship to the database could be invalidated, wholly or
> partially, by some other client acting before us.
>
> ovsdb_idl_txn_commit() tries to document this:
>
>  * Committing a transaction rolls back all of the changes that it made to the
>  * IDL's copy of the database.  If the transaction commits successfully, then
>  * the database server will send an update and, thus, the IDL will be updated
>  * with the committed changes. */
I get it now. Though in my case, the IDL does not seem to get updated
with the DB
value (which I guess is because they are all write_only columns).

>
> but it may not draw enough attention to it (the above is at the end of a
> very long comment) and it doesn't describe the reason.  Maybe I should
> update it.