Skip to content
Snippets Groups Projects
  1. Jul 18, 2014
  2. Jul 17, 2014
  3. Jul 16, 2014
  4. Jul 15, 2014
  5. Jul 14, 2014
  6. Jul 13, 2014
    • Konstantin Osipov's avatar
      A pre-requisite patch for multi-statement transactions. · 1d1b8953
      Konstantin Osipov authored
      Refactor statement transaction lifecycle. Avoid nested
      statement transactions. Make sure there is no more than 1
      statement transaction present in the system at the moment.
      
      Resolve the bugs this revealed:
      - in local hot standby we would parasite on the main or
      script fiber session to process requests. When an assert
      was added that there is no more than 1 transaction active
      at a given moment in time, it turned out that transactions
      running on behalf of local hot standby were running in
      the scope of session of the run_script or sched fibers.
      
      Create and use an own session there.
      
      - refactor session on_connect/on_disconnect trigger
      invocation: do not invoke these triggers for just any session,
      only for real connects/disconnects (iproto, admin).
      
      - split session creation/destruction and trigger invocation
      Conclude that session storage implementation needs to be
      done differently.
      1d1b8953
  7. Jul 11, 2014
  8. Jul 10, 2014
Loading