>From the "status" section at the bottom of the README for pq:

"This package is effectively in maintenance mode and is not actively
developed. Small patches and features are only rarely reviewed and merged.
We recommend using pgx which is actively maintained."

On Mon, Feb 22, 2021 at 7:19 AM Paul Förster <paul.foers...@gmail.com>
wrote:

> Hi,
>
> is there any important advantage of using github.com/jackc/pgx/v4 instead
> of github.com/lib/pq? I ask because in my view, pgx is bloated beyond
> repair.
>
> Please consider this:
>
> $ go clean --modcache
> $ du -sh ~/go/pkg; find ~/go/pkg -type f | wc -l
> 4.0K    ~/go/pkg
>        1
>
> $ go get github.com/lib/pq
> go: downloading github.com/lib/pq v1.9.0
> $ du -sh ~/go/pkg; find ~/go/pkg -type f | wc -l
> 712K    ~/go/pkg
>       74
>
> So, only 712K in 74 files, which is good. But:
>
> $ go clean --modcache
> $ du -sh ~/go/pkg; find ~/go/pkg -type f | wc -l
> 4.0K    ~/go/pkg
>        1
> $ go get github.com/jackc/pgx/v4
> go: downloading github.com/jackc/pgx v3.6.2+incompatible
> go: downloading github.com/jackc/pgx/v4 v4.10.1
> go: downloading github.com/jackc/pgio v1.0.0
> go: downloading github.com/jackc/pgconn v1.8.0
> go: downloading github.com/jackc/pgproto3 v1.1.0
> go: downloading github.com/jackc/pgtype v1.6.2
> go: downloading golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543
> go: downloading github.com/jackc/chunkreader v1.0.0
> go: downloading github.com/jackc/pgservicefile
> v0.0.0-20200714003250-2b9c44734f2b
> go: downloading github.com/jackc/pgpassfile v1.0.0
> go: downloading golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9
> go: downloading golang.org/x/text v0.3.3
> go: downloading github.com/jackc/pgproto3/v2 v2.0.6
> go: downloading github.com/jackc/chunkreader/v2 v2.0.1
> $ du -sh ~/go/pkg; find ~/go/pkg -type f | wc -l
>  56M    ~/go/pkg
>     2178
>
> 56M in 2178 files??? I just can't see the advantage of this, even though
> pgx obviously has more features. But that does not justify it being 80
> times as big, does it?
>
> Any thought beyond the usage of some data types which pgx can handle and
> pg can't?
>
> Cheers,
> Paul
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/F77C0E34-B761-4573-9E21-D4AE838527AC%40gmail.com
> .
>


-- 
*Matt Holiday*
Senior Gopher, Marketing Technologies

620 Eighth Avenue

New York, NY 10018

matthew.holi...@nytimes.com

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAGSa1CmNy-zgin24fEDyQvTvNzGTFrLkr6t10b58oxYzBiQyWg%40mail.gmail.com.

Reply via email to