Tres Seaver wrote:
> Shane Hathaway wrote:
>> However, I think we can still take advantage of listen and notify in a
>> slightly different way.  Currently, the Postgres adapter rolls back the
>> load transaction on every connection close, but if it instead leaves the
>> session idle with a transaction open, it would be safe for RelStorage to
>> sometimes ignore new changes and only roll back and poll after an async
>> notification arrives.  I could see scalability going way up that way, as
>> long as Postgres doesn't mind all the idle sessions with an open
>> transaction.
> Hmm, I think I read that NOTIFY events are only delivered between
> transactions, which would make that strategy unworkable.

Oops, you're right, that's an important detail.  This idea will need
more thought.


For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -

Reply via email to