Twitter's use of finagle-postgres

Twitter has relatively recently begun work on an internal project that will be using the PostgreSQL wire protocol, and are hoping to use finagle-postgres for that since it's a great project. Obviously, @vkostyukov (and more recently @steveniemitz and I suspect others) from Twitter have been contributing to the project, but we're interested in upping our involvement a bit.

The first question, mostly for @leonmaia but really any interested contributor or user of the project, is whether you're open to us stepping in to help with the maintenance of the project more. And then related to that, we wanted to propose the idea of promoting finagle-postgres to being a core part of the finagle project alongside [finagle-mysql](https://github.com/twitter/finagle/tree/develop/finagle-mysql), [finagle-redis](https://github.com/twitter/finagle/tree/develop/finagle-redis), etc. That would allow the CSL team inside of Twitter to more easily maintain it with the rest of Finagle to keep it in sync with any changes, etc.

Anyway, we really like the project and are excited about using it, and would love to help however we can. 🎉

Start by reviewing this proposal and the linked finagle-mysql directory to understand how database clients are organized within Finagle. Confirm whether maintainers want Twitter to help maintain finagle-postgres and whether it should become a core Finagle component; done requires an agreed ownership and integration decision.

Written by the indexing model from the issue text.