Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/pkgsite: explore using pgx for fast bulk inserts #42707

jba opened this issue Nov 18, 2020 · 2 comments

x/pkgsite: explore using pgx for fast bulk inserts #42707

jba opened this issue Nov 18, 2020 · 2 comments


Copy link

@jba jba commented Nov 18, 2020

Doing bulk inserts with pgx may be significantly faster than our current method of constructing large INSERT statements. Benchmark and switch to pgx if it's significantly better.

@jba jba added this to the pkgsite/unplanned milestone Nov 18, 2020
@jba jba self-assigned this Nov 18, 2020
gopherbot pushed a commit to golang/pkgsite that referenced this issue Nov 24, 2020
Add a benchmark which demonstrates that pgx's CopyFrom method
is significantly faster than doing a bulk insert with pq. In this
simple example, it is 55 times faster (!).

For golang/go#42707

Change-Id: I8bb37ba95b6207ead320b9720fbcc5a2fb8c8514
Trust: Jonathan Amsterdam <>
Run-TryBot: Jonathan Amsterdam <>
Reviewed-by: Julie Qiu <>
Copy link

@gopherbot gopherbot commented Nov 24, 2020

Change mentions this issue: internal/database: benchmark pgx copy against bulk insert

Copy link
Contributor Author

@jba jba commented Nov 25, 2020

pgx is faster, and it makes sense to switch to it for other reasons too (like, it's actively maintained). We now can use either the lib/pq or pgx drivers by setting an environment variable. We'll roll out pgx to the workers first, then the frontends. Once we're sure there are no issues with it, we can start using the fast copy code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.