Skip site navigation (1) Skip section navigation (2)

Re: The encoding problem of a server log.

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: "Dave Page" <dpage(at)pgadmin(dot)org>
Cc: "Magnus Hagander" <magnus(at)hagander(dot)net>,<pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: The encoding problem of a server log.
Date: 2009-01-18 13:05:22
Message-ID: A50B834DCD5A4786922F56B65F1D4983@HIRO57887DE653 (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers

> 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:  サーバが想定する符号化方式に合わないバイトシーケンスが存在した場合にもこ

>> 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.

Hiroshi Saito 

In response to

pgadmin-hackers by date

Next:From: Devrim GÜNDÜZDate: 2009-01-18 21:11:06
Subject: pgadmin3 removed from Fedora 10+
Previous:From: Dave PageDate: 2009-01-18 11:03:21
Subject: Re: The encoding problem of a server log.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group