Re: [PATCH] Patch to fix a crash of psql

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [PATCH] Patch to fix a crash of psql
Дата
Msg-id 50B8B042.7020301@gmx.net
обсуждение исходный текст
Ответ на Re: [PATCH] Patch to fix a crash of psql  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Ответы Re: [PATCH] Patch to fix a crash of psql  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCH] Patch to fix a crash of psql  (Tatsuo Ishii <ishii@postgresql.org>)
Список pgsql-hackers
On 11/30/12 3:26 AM, Albe Laurenz wrote:
> Tatsuo Ishii wrote:
>> postgres=# \i ~/sql
>> CREATE DATABASE
>> You are now connected to database "mydb" as user "t-ishii".
>> CREATE SCHEMA
>> psql:/home/t-ishii/sql:7: warning: possible conflict between client
> encoding SJIS and input file
>> encoding
>> CREATE TABLE
>>
>> Comments?
> 
> I wonder about the "possible".
> 
> Could there be false positives with the test?
> If yes, I don't like the idea.
> If there is no possibility for false positives, I'd say
> that the "possible" should go.  Maybe it should even be
> an error and no warning then.

Yes, encoding mismatches are generally an error.

I think the message should be more precise.  Nobody will know what an
"encoding conflict" is.  The error condition is "last multibyte
character ran over end of file" or something like that, which should be
clearer.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Pavan Deolasee
Дата:
Сообщение: Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger?
Следующее
От: Pavan Deolasee
Дата:
Сообщение: Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger?