Hi.
Can we at least detect the problem and warn the user? It might be
useful to provide a 'save log' button to allow the user to save the
raw log locally for further examination using other tools.
Ahh, It is useful to specify the reason which can't be displayed.
Also, note that I suggested to Guillaume (who is working on frmStatus)
that we should replace the listview used for the log with a text
control. That may be able to display the messed up encodings more
usefully.
Um, It seems that the problem can't be solved by pgAdmin. :-(
== Sorry, this is japanese ==
HIROSHI=# SELECT pg_file_read(filename, 0, 500) FROM pg_logdir_ls()
HIROSHI-# AS A(filetime timestamp, filename text) ORDER BY filetime ASC LIMIT
1;
ERROR: 符号化方式"UTF8"で無効なバイトシーケンスです: 0x83
HINT: サーバが想定する符号化方式に合わないバイトシーケンスが存在した場合にもこ
のエラーが発生します。これは"client_encoding"で制御されます。
HIROSHI=#
I consider the proposal of log_encoding(GUC) for the purpose of ver 8.5 or
over. However, adjustment is now difficult.... much time is needed for it.
Therefore, I wish to recognize this problem as TODO. or, are there some
ideas?
Only the workaround above (which I think we should consider now) :-(
Yeah, I hopeful it.
Thanks!
Regards,
Hiroshi Saito
--
Sent via pgadmin-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
