Re: [PATCH] Patch to fix a crash of psql - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Patch to fix a crash of psql
Date
Msg-id 50B8B042.7020301@gmx.net
Whole thread Raw
In response to Re: [PATCH] Patch to fix a crash of psql  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses 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>)
List 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 by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger?
Next
From: Pavan Deolasee
Date:
Subject: Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger?