Message-ID: <0af232bff681af8f34fd92ceb4d5c635e11815cb.camel@cybertec.at>
Subject: Re:  Is there any limit on the number of rows to import using copy
 command
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "sivapostgres@yahoo.com" <sivapostgres@yahoo.com>, Pgsql-general
	 <pgsql-general@postgresql.org>
Date: Wed, 23 Jul 2025 16:10:44 +0200
In-Reply-To: <959901171.1916220.1753271729336@mail.yahoo.com>
References: <1453510076.1900935.1753260637232.ref@mail.yahoo.com>
	 <1453510076.1900935.1753260637232@mail.yahoo.com>
	 <de08fd016dd9c630f65c52b80292550e0bcdea4c.camel@cybertec.at>
	 <959901171.1916220.1753271729336@mail.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-1.fc42) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/0af232bff681af8f34fd92ceb4d5c635e11815cb.camel%40cybertec.at>
Precedence: bulk

On Wed, 2025-07-23 at 11:55 +0000, sivapostgres@yahoo.com wrote:
> 1.=C2=A0 I tried running Copy From command from PGAdmin.=C2=A0=C2=A0
> 2.=C2=A0 I ran pg_stat_activity also in another tab [ PGAdmin ].
>=20
> What I observed,
> 1.=C2=A0 In about 2 min, in the Dashboard of PGAdmin, the colour changed =
to Orange for that particular pid.
> 2.=C2=A0 After few seconds, the colour again changed to Red.=C2=A0 =C2=A0
> 3.=C2=A0 The stat column in both Dashboard and pg_stat_activity.state sho=
ws 'active'.
> 4.=C2=A0 No messages relevant to this pid in postgres' log files
> 5.=C2=A0 CPU usage is normal, hovering around 36% overall, 15-18% for pos=
tgresql server, from the beginning and even after 3 min.
> 6.=C2=A0 We didn't run any other application in that machine.=C2=A0=C2=A0
> 7.=C2=A0 Unique Index is there in table2 which will return only one row f=
or that Select Count(*) query.
> 8.=C2=A0 No record is there in the target table when transfer started.=C2=
=A0 This transfer is the first batch for that particular table.
> 9.=C2=A0 Once color turned into Red, I could cancel the query execuion in=
 PGAdmin, which immediately stops the execution.
> 10. I could not see any locks or blocking pids.

As far as I know, red in pgAdmin (I don't use it) *is* the indication for a=
 wait event.
So look again what the columns "wait_event_type" and "wait_event" in "pg_st=
at_activity" show.

Yours,
Laurenz Albe