Robert

Ah good then, considering the "high priority" label I was worried that things might be on fire.

Meanwhile postgrest has migrated from configurator-ng to configurator-pg, so from that point of view this update is no longer necessary.

#9 would put the package closer to a state to be included with stackage.

Note that it's possible to un-fork a repository; as per https://help.github.com/en/articles/why-are-my-contributions-not-showing-up-on-my-profile#commit-was-made-in-a-fork github support seems to generally handle such requests quickly and smoothly.

The same failure occurs building on guix: http://ci.guix.gnu.org/log/4afh942h5ys60hixrnpfc8va7sjskmxd-ghc-libmpd-0.9.0.9

> LGTM! > > > Any specific reason why we still support GHC 8.10? > > Not one from my side. > > cc @robx None that I'm aware of...

Some performance results, using `postgrest-loadtest`. | | pipeline=yes | pipeline=no | main branch | | --- | --- | --- | --- | | pgdelay=0 | 300 | 287 |...

The library changes: - https://github.com/nikita-volkov/hasql/compare/master...robx:hasql:pipeline2 - https://github.com/nikita-volkov/hasql-transaction/compare/master...robx:hasql-transaction:pipeline - https://github.com/PostgREST/postgresql-libpq/compare/master...robx:postgresql-libpq:pipeline The `postgresql-libpq` change is essentially good to go upstream, but I haven't filed it yet.

I see, thanks for the info! It's in the logs, too ``` /usr/local/.ghcup/tmp/ghcup-27aab4df8c9b048c/usr/local/.ghcup/ghc/8.0.2/lib/ghc-8.0.2/bin/ghc-pkg: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory ```...

Coming from golang, there's a similar convention to python (standard library, third party, local). I like how gofmt handles this, which is to sort alphabetically within groups separated by empty...