On 22.06.22 22:18, Tomas Pospisek wrote:
On 22.06.22 21:25, Adrian Klaver wrote:
On 6/22/22 12:17, Tomas Pospisek wrote:
Hi all,
while doing `cat pg_dump.dump | psql` I get the above message. Note
that `pg_dump.dump` contains:
CREATE DATABASE some_db WITH TEMPLATE = my_own_template ENC
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
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
On 6/23/22 00:37, Tomas Pospisek wrote:
On 22.06.22 22:18, Tomas Pospisek wrote:
On 22.06.22 21:25, Adrian Klaver wrote:
On 6/22/22 12:17, Tomas Pospisek wrote:
So I used both pg_dump and pg_restore from the newer machine. Result is
still the same. So I'll use Tom Lane's suggestion too an
On 6/23/22 10:11, Adrian Klaver wrote:
On 6/23/22 00:37, Tomas Pospisek wrote:
On 22.06.22 22:18, Tomas Pospisek wrote:
On 22.06.22 21:25, Adrian Klaver wrote:
On 6/22/22 12:17, Tomas Pospisek wrote:
So I used both pg_dump and pg_restore from the newer machine. Result
is still the same.
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-
