Re: PQexecPrepared() question
| От | Igor Korot |
|---|---|
| Тема | Re: PQexecPrepared() question |
| Дата | |
| Msg-id | CA+FnnTyYBNwbzFs5GqO+SMg3g60jPTsnmFwTV=_s_YboGo-68A@mail.gmail.com обсуждение исходный текст |
| Ответ на | PQexecPrepared() question (Igor Korot <ikorot01@gmail.com>) |
| Ответы |
Re: PQexecPrepared() question
|
| Список | pgsql-general |
Hi, ALL,
On Fri, Dec 19, 2025 at 9:17 AM Igor Korot <ikorot01@gmail.com> wrote:
Hi, Lauren’s,On Thu, Dec 18, 2025 at 11:43 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:On Thu, 2025-12-18 at 07:20 -0800, Igor Korot wrote:
> Imagine following scenario:
>
> I have 2 machines. One is running PG server on *nix. Second is my app on Windows.
>
> An application starts for the first time.
>
> What is “clientencoding in this case?
If I read the code correctly:
- if PGCLIENTENCODING is set in the environment of the client executable, thatNo it is not.
- otherwise, if "client_encoding" is set on the server, that
I just checked the postgres.conf.
This file does not have any client_encoding.
I guess I is.But what is the purpose of setting client encoding on the server? It is for the clientThank you.
- otherwise, SQL_ASCII
Which means that this is an encoding that will be used.
But then I don’t understand anything.
The code I posted above worked fine on SELECT, but INSERT failed.
If the SQL_ASCII is the encoding used both operations should fail. Or both succeeds.
Could someone explain what happened?
Thank you.
Yours,
Laurenz Albe
В списке pgsql-general по дате отправления: