1. 26 8月, 2020 1 次提交
  2. 25 8月, 2020 1 次提交
  3. 22 8月, 2020 1 次提交
  4. 21 8月, 2020 2 次提交
  5. 19 8月, 2020 6 次提交
  6. 14 8月, 2020 1 次提交
    • J
      fix(cutlass): pg-wire improvements. Fixes #450 (#544) · 5fad98cf
      Joan Augsburger 提交于
      This change deals with issues around protocol mechanics, in particular our responses to messages from the client on simple and extended mode.
      
      For example:
      
      - we now wait for sync message to send reply back, therefore grouping replies. This means that if client sends messages: P/B/D/E/S, we now send one reply back with 1/2/T/D/C/Z. This means that there is less chatter on the wire because 1. we are sending less messages and 2. the client does not get confused and therefore send less messages.
      - for each message sent by client, we send an acknowledgement back
      - stop sending spurious messages
      - named prepared statements are cached on parse and we correctly bind parameters when receiving named statement on the Bind and Describe messages
      - when executing 'select', we now send back the number of returned rows
      - when executing 'set', we now send correct query tag (SET)
      - for empty queries, we reply back with correct message type
      - for queries with no data, we reply back with 'no data' message type
      - row description now includes column number
      - row descriptions attempts to populate type size and type modifier
      5fad98cf
  7. 12 8月, 2020 2 次提交
  8. 11 8月, 2020 1 次提交
  9. 10 8月, 2020 2 次提交
    • V
      fix(griffin): fixed 'with' clause behaviour in set operations (union, expct,... · ba84978a
      Vlad Ilyushchenko 提交于
      fix(griffin): fixed 'with' clause behaviour in set operations (union, expct, intersect), in recursive 'with' and in sub-queries (#541)
      
      ba84978a
    • V
      chore: simplified embedded API (#539) · b0890613
      Vlad Ilyushchenko 提交于
      I had to move telemetry queue and sequences to CairoEngine. Leaving them on MessageBus would cause problem when various components run with local pools. In this scenario there are multiple copies of MessageBus and it would be unnacceptable to have multiple queues for telemetry. Only one queue would be consumed and all others stalling.
      
      Additionally requiring PropServerConfiguration for very simple embedded setup was unreasonable. Telemetry should be ok with CairoConfiguration.
      
      I moved MessageBus instance inside CairoEngine. They are created based on the same configuration now and they are used in 1-to-1 combination most of the time. Except of course for those pesky local pools. The components that can have local thread pool use separate instance of MessageBus.
      b0890613
  10. 07 8月, 2020 4 次提交
  11. 04 8月, 2020 1 次提交
  12. 03 8月, 2020 3 次提交
  13. 31 7月, 2020 1 次提交
  14. 29 7月, 2020 2 次提交
  15. 28 7月, 2020 1 次提交
  16. 27 7月, 2020 4 次提交
  17. 24 7月, 2020 1 次提交
  18. 23 7月, 2020 1 次提交
  19. 22 7月, 2020 4 次提交
  20. 18 7月, 2020 1 次提交