Re: libpq and mysterious "invalid byte sequence for encoding UTF8".

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rob stone <floriparob(at)gmail(dot)com>
Cc: Jiří Pavlovský <jiri(at)pavlovsky(dot)eu>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: libpq and mysterious "invalid byte sequence for encoding UTF8".
Date: 2021-02-02 02:53:45
Message-ID: 3597100.1612234425@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

rob stone <floriparob(at)gmail(dot)com> writes:
> Columns:- maincontact boolean DEFAULT false,
> publdatacontact boolean DEFAULT false,
> invcontact boolean DEFAULT false,
> queries_recipient boolean,
> fakelastname boolean NOT NULL DEFAULT false,

> are defined as booleans and all except one have defaults declared, yet
> you are passing NULL's which the insert tries to cast to boolean.
> Maybe this is the cause of the error??

Oooh ... if we posit that the statement is expected to throw an error,
maybe what this error is complaining about is an inability to translate
a localized error message to the client's encoding. This could reflect
an incorrectly-encoded .po file, for example. So what we need to know
next is what lc_messages setting Jiří is using, and also the server
and client encodings.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jain, Ankit 2021-02-02 03:05:55 Issues with using plpgsql debugger using PG13 on Centos 7
Previous Message Matt Zagrabelny 2021-02-02 02:31:31 Re: count(*) vs count(id)