> "Hiroshi Saito" <z-saito@guitar.ocn.ne.jp> writes:
>> I understand the essence which you say. Then, I think that gmtime is an ideal
>> there. localtime also takes summer time into consideration. It changes and
>> sometimes falls unconsciously. Furthermore, a tzname can't be expressed
>> by the present elog....
>> Moreover, how about relocating datacenter to New York from the loss Angelus?
>> The log is continued.... database log is an audit item. Recently, it is more
>> important than a response. And it is used secondarily.
>
> People who find the above arguments compelling would certainly be free
> to set their log_timezone to GMT. Those who don't find them compelling
> should not be forced to deal in GMT. The fact that Postgres has always
> logged in system local time, and we've had no complaints about that,
> suggests to me that most people prefer local-time logging.
A certain user said. timezone of GUC is not effective with an elog output.....
I am, though it is an ideal that there is (e)log_timezone which you say.:-)
Um, I think that only for PostgreSQL is good.
BTW, windows user should do how.?
Regards,
Hiroshi Saito
