Am 27.06.2022 um 12:12 schrieb Daniel Verite:
WR wrote:
First run worked.
Second run worked.
Then I changed to SET standard_conforming_strings = off;
Third run worked.
Fourth run throw the error
Then I changed back to SET standard_conforming_strings = on;
Fifth run throw the error too.
WR wrote:
> First run worked.
> Second run worked.
> Then I changed to SET standard_conforming_strings = off;
> Third run worked.
> Fourth run throw the error
> Then I changed back to SET standard_conforming_strings = on;
> Fifth run throw the error too.
> And only adding E and second bac
Am 27.06.2022 um 09:32 schrieb David G. Johnston:
[snip]
I suggest doing self-contained examples that demonstrate the documented
behavior not working as documented (or not being functional even if
intended) to pinpoint any bug that might be lurking here. With only
fragments and statements t
On Sunday, June 26, 2022, WR wrote:
>
> I made some test with pgadmin. Pgadmin (5.2) also reports this error now.
> And it doesn't matter if standard_conforming_strings is on or off.
>
>
> SET standard_conforming_strings = off;
>
> INSERT INTO public.oned_figures VALUES (1, 'Figure_Wolle1', 476,
Another strange thing is:
in my first mail I wrote: running the dump in in pgadmin works, in the
last mail I wrote pgadmin also produces the error. I played a little bit
how this could be happend.
Everytime ich used the following sql text in the querytool:
SET standard_conforming_strings = o
I'm back at my problem today:
Example:
postgres=# set standard_conforming_strings to off;
SET
postgres=# set escape_string_warning to off;
SET
postgres=# select '\000'::bytea;
ERROR: invalid byte sequence for encoding "UTF8": 0x00
postgres=# select '\\000'::bytea;
bytea
---
\x
WR wrote:
> But one question is left.
>
> When I read this valid data into a c++ std::string (and I checked that
> the single backslashes are still there). Why can't I put this
> SQL-command to a pqxx-transaction and execute it. It looks like the
> pqxx-transaction unescapes the bytea-
Am 23.06.2022 um 17:13 schrieb WR:
Hello community,
I've some trouble in restoring a plain text pg_dump.
Postgres version is 13 x64 running on Windows10x64 installed from EDB
package.
The database has bytea_output = 'escape' option because of some
processing software needs it for historical
Hello community,
I've some trouble in restoring a plain text pg_dump.
Postgres version is 13 x64 running on Windows10x64 installed from EDB
package.
The database has bytea_output = 'escape' option because of some
processing software needs it for historical reasons.
Dump command is:
pg_dump
