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

COPY progress reporting is not supported #40

Open
onderkalaci opened this issue Oct 8, 2024 · 1 comment
Open

COPY progress reporting is not supported #40

onderkalaci opened this issue Oct 8, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@onderkalaci
Copy link

When you normally do COPY FROM/TO on heap tables, they show up in pg_stat_progress_copy view.

With pg_parquet, when I do COPY .. TO .. (parquet), the view is not populated:

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:

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
@onderkalaci onderkalaci added the enhancement New feature or request label Oct 8, 2024
@aykut-bozkurt
Copy link
Collaborator

Our custom parquet dest receiver api does not update copy progress stats table. 2 solutions:

  • It would be updated by Postgres if we switch into callback api as we do for COPY FROM,
  • We manually update the stats table.

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

No branches or pull requests

2 participants