We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When you normally do COPY FROM/TO on heap tables, they show up in pg_stat_progress_copy view.
COPY FROM/TO
pg_stat_progress_copy
With pg_parquet, when I do COPY .. TO .. (parquet), the view is not populated:
COPY .. TO .. (parquet)
select * from pg_stat_progress_copy; (0 rows)
When I do COPY .. FROM (parquet), bytes_total is not populated, which is making the progress reporting less useful than it could be:
COPY .. FROM (parquet)
bytes_total
select * from pg_stat_progress_copy; -[ RECORD 1 ]----+---------- pid | 60146 datid | 5 datname | postgres relid | 24770 command | COPY FROM type | CALLBACK bytes_processed | 389524432 bytes_total | 0 tuples_processed | 22978000 tuples_excluded | 0 tuples_skipped | 0
The text was updated successfully, but these errors were encountered:
Our custom parquet dest receiver api does not update copy progress stats table. 2 solutions:
COPY FROM
Sorry, something went wrong.
No branches or pull requests
When you normally do
COPY FROM/TO
on heap tables, they show up inpg_stat_progress_copy
view.With pg_parquet, when I do
COPY .. TO .. (parquet)
, the view is not populated:When I do
COPY .. FROM (parquet)
,bytes_total
is not populated, which is making the progress reporting less useful than it could be:The text was updated successfully, but these errors were encountered: