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
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
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
Am 03.05.2021 um 10:41 schrieb Laurenz Albe:
On Sat, 2021-05-01 at 12:59 +0200, Wolfgang Rißler wrote:
Am 30.04.2021 um 16:16 schrieb Tom Lane:
I would recommend trying to use a reasonably late-vintage libpq; we do
fix bugs in it on a regular basis.
The common stumbling block for cross-version
Hello community,
actually I have a problem wit PG13 on Windows 10 (both x64), Postgres
version is 13.0.2.21090 from EDB installer.
I have to develop a logical replication cluster, where sometimes there
happens a shutdown of one host. Logical replication works nice, thank
you for that.
My i
Hello Vijaykumar Jain,
thank you for fast answer, today I'm not able to access the hardware,
I'll be back tomorrow and will do the required tests.
Wolfgang
Am 21.07.2021 um 15:14 schrieb Vijaykumar Jain:
select pg_stat_reset();
Can you run above function, to check if stats are reset and thi
Hello Vijaykumar Jain,
at first: select pg_stat_reset(); doesn't help, the pg_stat_activity is
the same after it.
I added some interesting rows after two reboots (which have been
complete power cycles)
artea=# select pid ,application_name , client_addr ,client_port
,backend_start ,query_st
gards,
Ninad Shah
On Wed, 21 Jul 2021 at 19:15, WR <mailto:wolle...@freenet.de>> wrote:
Hello Vijaykumar Jain,
thank you for fast answer, today I'm not able to access the hardware,
I'll be back tomorrow and will do the required tests.
Wolfgang
Am 21.
I also looked for the shutdown mode:
since there is no -m parameter in the commandline for starting the
windows-postgres-service, the shutdown mode seems to be the default:
fast
Am 21.07.2021 um 15:14 schrieb Vijaykumar Jain:
select pg_stat_reset();
Can you run above function, to check if
from EDB.
Wolfgang
Am 22.07.2021 um 11:04 schrieb Vijaykumar Jain:
On Thu, 22 Jul 2021 at 12:41, WR <mailto:wolle...@freenet.de>> wrote:
Hello Vijaykumar Jain,
at first: select pg_stat_reset(); doesn't help, the pg_stat_activity is
the same after it.
one thing, i forgot
lf has a number of issues. Hence, it is always
suggested to use Linux with it.
It can be explored further by querying the table from which
pg_stat_activity gathers data.
Regards,
Ninad Shah
On Thu, 22 Jul 2021 at 12:51, WR <mailto:wolle...@freenet.de>> wrote:
Hello Ninad Sh
quot;idle in transaction" and "idle" are different
terms. "Idle in transaction" refers to connections that are waiting for
either commit or rollback.
Additionally, this could be a bug as well. However, it's difficult to
conclude at this stage. You may report this to
13 matches
Mail list logo
