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

The problem with the end of the process when working with big data . #86

Closed
andrydl opened this issue Jul 1, 2016 · 1 comment
Closed

Comments

@andrydl
Copy link

andrydl commented Jul 1, 2016

The process pg_repack is not completed until the work previously running transactions. Even if they are not related to repacking tables. If before pg_repack starting "autovacuum analyze" another table, it wait ending "autovacuum analyze". But if the table has a size several terabytes , then the wait will be very long (several days). In pg_stat_activity row "SELECT pid FROM pg_locks WHERE locktype = 'virtualxid' AND pid <> pg_backend_pid() AND virtualtransaction = ANY($1) " or "SELECT repack.repack_apply($1, $2, $3, $4, $5, $6)". I think it's wrong to wait for the completion of all previously started transaction.Moreover, they are not related to the processed table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants