-
Notifications
You must be signed in to change notification settings - Fork 178
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
'utf-8' codec can't decode byte 0xf8 in position 0 #130
Comments
Could you try with |
Seems the error come from |
* This commit attenpts to solve issue : dalibo#130. * PoWA has a bug where backend_type is not correctly filled. it was fixed but it's not in the stable version yet. * Previously, we queried for the `backend_type` and filtered `parallel workers` in the Python code. The test is now done in SQL, which avoids the problems all together. * The `parallel worker` detection was not working for pg 11+ because it uses the 'parallel worker' backend_type. It's now fixed.
* This commit attenpts to solve issue : dalibo#130 [1]. * PoWA has a bug where backend_type is not correctly filled [2]. it was fixed but it's not in the stable version yet. * Since [3], we queried for the `backend_type` and filtered `parallel workers` in the Python code. The test is now done in SQL, which avoids the problems all together. * The `parallel worker` detection was not working for pg 11+ because it uses the 'parallel worker' backend_type. It's now fixed. [1] dalibo#130 [2] powa-team/powa-archivist#20 [3] dalibo@6a180d8
* This commit attempts to solve the issue : dalibo#130 [1]. * PoWA has a bug where `backend_type` is not correctly filled [2]. it was fixed but it's not in the stable version yet. * Since [3], we queried for the `backend_type` and filtered `parallel workers` in the Python code. The test is now done in SQL, which avoids the problems all together. * The `parallel worker` detection was not working for pg 11+ because it uses the 'parallel worker' backend_type. It's now fixed. [1] dalibo#130 [2] powa-team/powa-archivist#20 [3] dalibo@6a180d8
Hi, The problem is related to this issue : powa-team/powa-archivist#20 The backend_type is wrong : 10.20.40.50:5432 powa@postgres=# SELECT application_name, backend_type FROM pg_stat_activity \gx -[ RECORD 1 ]----+-------------------------------- application_name | PoWA collector backend_type | pm\x7F Which triggers : UnicodeDecodeError('utf-8', b'pm\xa7\x95\xff\x7f', 2, 3, 'invalid start byte') The PR attempts to fix this. Benoit. |
The PR was merged, can you try it ? |
Fixed |
Since the installation of
powa
, I got error withpg_activity
script whereas I'm using it for years without a single error.The text was updated successfully, but these errors were encountered: