Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #4196: Backend crash possible with psql
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #4196: Backend crash possible with psql
- Date: Mon, 26 May 2008 12:10:41 -0400
- Message-id: <22282(dot)1211818241(at)sss(dot)pgh(dot)pa(dot)us>
Oh, one other thing: if the theory about gettext delivering the "wrong" encoding is correct, then the error messages going into the postmaster log should be in WIN1252 encoding, rather than UTF8 which is the intended behavior when server_encoding is UTF8. The log snippet in your bug report was UTF8, but that might have gotten converted somewhere along the line. Can you confirm which encoding is actually present in the log file? regards, tom lane
- References:
- BUG #4196: Backend crash possible with psql
- From: Daniel Mihowski
- Re: BUG #4196: Backend crash possible with psql
- From: Tom Lane
- Re: BUG #4196: Backend crash possible with psql
- From: Daniel Migowski
- BUG #4196: Backend crash possible with psql
- Prev by Date: Re: BUG #4196: Backend crash possible with psql
- Next by Date: Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Previous by thread: Re: BUG #4196: Backend crash possible with psql
- Next by thread: Re: BUG #4196: Backend crash possible with psql
- Indexes: