Sergey Prokhorov

@bullno1 btw, regarding decimal... Have you noticed that codecs might be parametrized? So it might make sense to keep binary decoding in a main repo, but allow it being parametrized...

Looks like we got 1st "foreign" pluggable datatype implemented: https://github.com/egobrain/epgsql_decimal and https://hex.pm/packages/epgsql_decimal :tada:

Hi. What's special about this kind of error is that it is returned at the same time when connection process exits with non-normal reason: https://github.com/epgsql/epgsql/blob/95b02f29664bc793d39db3a6576b045dd8b446f7/src/commands/epgsql_cmd_connect.erl#L83 That usually means, since epgsql...

Are you sure we are bound to some specific version of PostgreSQL server? Is it hardcoded or asserted somewhere? My you, please, point me there?

Ok, nice! BTW, I don't have anything against docker image. But I don't have any experience with it yet. So, if you can make a pull-request it's ok.

Please, note that in #130 tests were converted to common_test.

Yep, sounds good. At least elixir driver have generic range implementation https://github.com/elixir-ecto/postgrex/blob/master/lib/postgrex/extensions/range.ex I think it may be implemented in the way how arrays are implemented (some time ago epgsql had...

I think we may introduce some connection option like `{type_opts, [{range, ...}, {timestamp, ...}]}` to change type encoding/decoding behaviour. We have also #109, which may solve this. But I don't...

@ElectronicRU would be nice. Do you think we should use github's Wiki page for design doc?

Hi. Thank you for your report. I'll look into this in a few days.