Re: 65279 Invisible ASCII Character

From: ramsiddu007 <ramsiddu007(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: 65279 Invisible ASCII Character
Date: 2018-07-17 10:25:11
Message-ID: CA+zEy78wpcgN3W+46E3E1030vZZzCOe-sWqKeNze9i-svjNs9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general pgsql-hackers

Thanks, I'll look into it.

On Tue, Jul 17, 2018 at 3:42 PM Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>
wrote:

> ## ramsiddu007 (ramsiddu007(at)gmail(dot)com):
>
> > If i remove first character it's run. That first
> > character is invisible, I have checked that *ascii* value, it is *65279*.
>
> That's not an ASCII-value, ASCII has 8 bits at most.
> What you've got there is a UTF-16 Byte Order Mark: 65279 is 0xfeff
> (one of the well-known constants).
> I'd suggest you get your editor configured to write files without
> BOM. Maybe there's a workaround via locale settings - but I have
> no machine with an UTF-16 locale available. Another approach is using
> recode on your files before concatenating.
>
> This question isn't really for pgsql-hackers - I'm redirecting to -general.
>
> Regards,
> Christoph
>
> --
> Spare Space
>

--
*Best Regards:*
Ramanna Gunde

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message arvind chikne 2018-07-17 12:01:34 Master slave replication
Previous Message Christoph Moench-Tegeder 2018-07-17 10:12:47 Re: 65279 Invisible ASCII Character

Browse pgsql-general by date

  From Date Subject
Next Message Fabio Pardi 2018-07-17 11:07:44 Re: Query to monitor index bloat
Previous Message Christoph Moench-Tegeder 2018-07-17 10:12:47 Re: 65279 Invisible ASCII Character

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-07-17 10:32:57 Re: file cloning in pg_upgrade and CREATE DATABASE
Previous Message Christoph Moench-Tegeder 2018-07-17 10:12:47 Re: 65279 Invisible ASCII Character