Ron writes:
> On 10/20/22 10:02, Adrian Klaver wrote:
>> 3) What if you run without --jobs?
> It runs without error. Add "--jobs=2" and the errors appear.
That's ... suggestive ... but not suggestive enough. Can you
create a self-contained test case? It probably doesn't depend
much at all on
On 10/22/22 17:06, Adrian Klaver wrote:
On 10/22/22 14:45, Ron wrote:
On 10/22/22 16:29, Adrian Klaver wrote:
To pseudo for me.
What file exactly is:
pg_restore --jobs=X --no-owner $NEWDB
restoring?
And how was that file created?
Knowing this might help get at why the more straight forwa
On 10/22/22 14:45, Ron wrote:
On 10/22/22 16:29, Adrian Klaver wrote:
To pseudo for me.
What file exactly is:
pg_restore --jobs=X --no-owner $NEWDB
restoring?
And how was that file created?
Knowing this might help get at why the more straight forward method
does not work.
This is what
On 10/22/22 16:29, Adrian Klaver wrote:
On 10/22/22 14:02, Ron wrote:
On 10/22/22 12:00, Adrian Klaver wrote:
On 10/22/22 09:41, Ron wrote:
On 10/22/22 11:20, Adrian Klaver wrote:
On 10/20/22 14:34, Ron wrote:
On 10/20/22 10:02, Adrian Klaver wrote:
On 10/20/22 06:20, Ron wrote:
On 10/20/2
On 10/22/22 14:02, Ron wrote:
On 10/22/22 12:00, Adrian Klaver wrote:
On 10/22/22 09:41, Ron wrote:
On 10/22/22 11:20, Adrian Klaver wrote:
On 10/20/22 14:34, Ron wrote:
On 10/20/22 10:02, Adrian Klaver wrote:
On 10/20/22 06:20, Ron wrote:
On 10/20/22 00:12, Tom Lane wrote:
I was afrai
On 10/22/22 12:00, Adrian Klaver wrote:
On 10/22/22 09:41, Ron wrote:
On 10/22/22 11:20, Adrian Klaver wrote:
On 10/20/22 14:34, Ron wrote:
On 10/20/22 10:02, Adrian Klaver wrote:
On 10/20/22 06:20, Ron wrote:
On 10/20/22 00:12, Tom Lane wrote:
I was afraid you were going to say that.
ertan.kucuko...@1nar.com.tr schrieb am 20.10.2022 um 21:59:
Hello,
I am using PostgreSQL v14.5 on Linux Debian 11.5. I recently observe very
high CPU usage on my Linux system as below
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+
COMMAND
2357756 postgres 20 0 244103
On 10/22/22 09:41, Ron wrote:
On 10/22/22 11:20, Adrian Klaver wrote:
On 10/20/22 14:34, Ron wrote:
On 10/20/22 10:02, Adrian Klaver wrote:
On 10/20/22 06:20, Ron wrote:
On 10/20/22 00:12, Tom Lane wrote:
I was afraid you were going to say that.
The work-around is to:
pg_dump $SRCDB --s
On 10/22/22 11:20, Adrian Klaver wrote:
On 10/20/22 14:34, Ron wrote:
On 10/20/22 10:02, Adrian Klaver wrote:
On 10/20/22 06:20, Ron wrote:
On 10/20/22 00:12, Tom Lane wrote:
I ran "pg_dumpall --globals-only --no-role-passwords" on the source
instance, and applied it to the new instance bef
On 10/20/22 14:34, Ron wrote:
On 10/20/22 10:02, Adrian Klaver wrote:
On 10/20/22 06:20, Ron wrote:
On 10/20/22 00:12, Tom Lane wrote:
I ran "pg_dumpall --globals-only --no-role-passwords" on the source
instance, and applied it to the new instance before doing the
pg_restore. If I hadn't do
On 10/20/22 12:59, ertan.kucuko...@1nar.com.tr wrote:
Hello,
I am using PostgreSQL v14.5 on Linux Debian 11.5. I recently observe very
high CPU usage on my Linux system as below
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+
COMMAND
2357756 postgres 20 0 2441032 2,
Hi,
I have a question. Its stays at the intersection of software engineering
and PostgreSQL.
I have configured streaming synchronous replication and whit setting
"synchronous_commit=remote_apply" to make sure that the slave will always
respond the same as the MASTER (this is a developers' requir
On 2022-10-20 09:56:23 -0700, Christophe Pettus wrote:
> On Oct 20, 2022, at 09:52, Vince McMahon
> wrote:
> > The number of rows are different.
>
> This isn't unexpected. EXPLAIN does not actually run the query and
> determine how many rows are returned; it calculates an estimate based
> on t
13 matches
Mail list logo
