pgx VS pq

I don't think so, but you should look at https://github.com/jackc/pgx which have low level features maybe for replication ?

The way it parses dates using Unix time causes issues when you compare the values returned due to Go setting the location property:

https://github.com/jackc/pgx/issues/863

pgx doesn't seem to handle reconnects the same way lib/pg does, but I haven't tested this recently: https://github.com/jackc/pgx/issues/672

String manipulation could lead to nasty SQL injections and really because you're using pgx there's no need to do that either, see the Conn.SendBatch method, it should allow you to achieve what you're trying to do: execute multiple queries in a transaction and still get their results. (test example)

pgx

In the process of trying to get better with Go, I have been trying to create a program that will scrape a subreddit and then save some info into a Postgres table. In this case, I decided to use r/frugalmalefashion and save the title and flair of recent posts into the table. I am using Colly to scrape data, and pgx as the database driver.

Connecting from my golang app via pgx database driver inside Docker (Alpine linux image) on my windows dev system: < 1s -> fast

> What kind of language recommends[0] with a straight face that you just duplicate your entire codebase into a v2/ subdirectory?

Not Go at least. You misunderstood the post completely.

Here is an example of how you are supposed to change the import path for subsequent major versions (that is, backwards incompatible versions): https://github.com/jackc/pgx/blob/3599f646293c1b0d381214ab26...

A one-line change to your modfile and the import path is changed.

Pass on the frameworks at first. just use the std library's net/http package and maybe a really basic router like julien schmidt's httprouter(https://github.com/julienschmidt/httprouter) to do your requests and use pgx(https://github.com/jackc/pgx) for postrgres.

postgres in go I've mostly seen done with pgx which kind of skates around the typical database/sql method. It's better maintained and faster than the more 'official' postgres driver, but I kind of hated using it.

For convenience, it is better to use https://github.com/lib/pq in conjunction with https://github.com/jmoiron/sqlx, you will have all the data in json

So, write your code such that swapping in a replacement driver, such as https://github.com/lib/pq is as painless as possible

The article mentions that lib/pq is "effectively in maintenance mode". This surprised me, I've never had problems with it, and looking at the commits on github [1] it seems far from inactive.

[1] https://github.com/lib/pq/commits/master

You can look up a commonly used Postgres driver for more info: https://github.com/lib/pq

I will initialize go modules and get (pq)[https://github.com/lib/pq] which is a pure Go postgres driver. Why do we use postgres driver for CockroachDB? CockroachDB supports PostgreSQL wire protocol. This means it is almost fully compatible with postgres drivers and ORMs.

I'll show how to connect to YugabyteDB and that's also the occasion to connect to YB from the Go driver (pq). What I do here with the YSQL connection can be done the same on a PostgreSQL database.

Here is link number 1 - Previous text "pg"