Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional PostgreSQL stores #23

Open
zloster opened this issue Apr 6, 2017 · 2 comments
Open

Additional PostgreSQL stores #23

zloster opened this issue Apr 6, 2017 · 2 comments
Milestone

Comments

@zloster
Copy link
Owner

zloster commented Apr 6, 2017

For quite a while there are:

  • hstore (string key, value pairs)
  • JSON (since 9.2 but seems like a little half-baked, see the link below, depends on the use-cases)
  • JSONB (since 9.4, best full feature integration)
  • UNLOGGED SQL tables - they skip the WAL and are not safe for data in case of crash. They are automatically truncated when crash is detected - so they are quite good for temporary data.

It will be interesting to see these against MongoDB.

Introduction here: https://www.citusdata.com/blog/2016/07/14/choosing-nosql-hstore-json-jsonb/

@zloster zloster added this to the BetterTimes milestone Apr 6, 2017
@zloster
Copy link
Owner Author

zloster commented Apr 25, 2017

I've tried to update PostgreSQL to 9.6 from the APT repository of PostgreSQL Global Development Group. The test results for the same framework were quite slower than the 9.3 from the Ubuntu 14.04 APT repository.
I need to check if the configuration settings for the PostgreSQL instance were in effect - I haven't check if the actual filesystem locations are the same. The benchmark toolset is copying the configuration file to predefined directory.

zloster pushed a commit that referenced this issue Oct 2, 2018
Here's an example of the error output from before this change:

Unhandled exception:
Bad state: Stream was already listened to
#0      _RawServerSocket.listen (dart:io-patch/socket_patch.dart:1106)
#1      new _ForwardingStreamSubscription (dart:async/stream_pipe.dart:123)
#2      _ForwardingStream._createSubscription (dart:async/stream_pipe.dart:91)
#3      _ForwardingStream.listen (dart:async/stream_pipe.dart:86)
#4      _ServerSocket.listen (dart:io-patch/socket_patch.dart:1351)
#5      _HttpServer.listen (dart:io/http_impl.dart:2278)
#6      _startServer.<anonymous closure> (file:///server.dart:88:12)
#7      _RootZone.runUnary (dart:async/zone.dart:1371)
#8      _FutureListener.handleValue (dart:async/future_impl.dart:129)
#9      _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:636)
#10     _Future._propagateToListeners (dart:async/future_impl.dart:665)
#11     _Future._completeWithValue (dart:async/future_impl.dart:478)
#12     Future.wait.<anonymous closure> (dart:async/future.dart:362)
#13     _RootZone.runUnary (dart:async/zone.dart:1371)
#14     _FutureListener.handleValue (dart:async/future_impl.dart:129)
#15     _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:636)
#16     _Future._propagateToListeners (dart:async/future_impl.dart:665)
#17     _Future._completeWithValue (dart:async/future_impl.dart:478)
#18     Future.wait.<anonymous closure> (dart:async/future.dart:362)
#19     _RootZone.runUnary (dart:async/zone.dart:1371)
#20     _FutureListener.handleValue (dart:async/future_impl.dart:129)
#21     _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:636)
#22     _Future._propagateToListeners (dart:async/future_impl.dart:665)
#23     _Future._completeWithValue (dart:async/future_impl.dart:478)
#24     _Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:510)
#25     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#26     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
#27     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:99)
#28     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:152)
@zloster
Copy link
Owner Author

zloster commented Apr 23, 2019

PostgreSQL is now updated to 11.x release. There are some ups and downs in the results but nothing stands out currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant