Please don't top-post.
On 6/3/19 6:26 AM, soumik.bhattacharjee@xxxxxxx wrote:
> My pg_restore is stuck here for last 2 days.
>
> pg_restore: creating CONSTRAINT "schema_name.num_servicenummer_historie snh_prx"
Consuming CPU and disk IO, or just sitting there?
Just sitting there and IO is more i think.
Mem: 28380592K used, 33300260K free, 686312K shrd, 714616K buff, 6628188K cached
CPU: 4% usr 4% sys 0% nic 0% idle 90% io 0% irq 0% sirq
Load average: 103.07 103.43 103.69 6/2316 3108
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
16 1 postgres S 203m 0% 5 0% postgres: autovacuum launcher process
18 1 postgres S 202m 0% 4 0% postgres: bgworker: logical replication launcher
1 0 postgres S 202m 0% 2 0% postgres
14 1 postgres S 202m 0% 8 0% postgres: writer process
15 1 postgres S 202m 0% 3 0% postgres: wal writer process
13 1 postgres S 202m 0% 4 0% postgres: checkpointer process
17 1 postgres S 62544 0% 7 0% postgres: stats collector process
And below -
bash-4.4$ netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54638 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54402 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54166 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54070 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54252 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54420 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54186 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54134 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54054 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54366 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54484 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54514 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54602 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54278 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54536 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54020 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
tcp 0 0 postgresdb-numuat-postgresql-6cf69984-dqhz5:54294 postgresdb-numuat-postgresql-6cf69984-dqhz5:postgresql TIME_WAIT
udp 0 0 localhost:36518 localhost:36518 ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
bash-4.4$
> -----Original Message-----
> From: Ron <ronljohnsonjr@xxxxxxxxx>
> Sent: Monday, June 03, 2019 1:24 PM
> To: pgsql-admin@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: ERROR:::::: could not rename temporary statistics file ...
>
> On 6/3/19 4:46 AM, soumik.bhattacharjee@xxxxxxx wrote:
>> Hello,
>>
>> While doing a restore from pgadmin, getting the below error- it's like 12GB restore file.
>>
>> Any pointers to solve this issue.
>>
>>
>>
>> 2019-06-03 09:01:39.978 UTC [17] LOG: could not rename temporary statistics file "pg_stat_tmp/db_13015.tmp" to "pg_stat_tmp/db_13015.stat": No such file or directory
>> 2019-06-03 09:01:40.090 UTC [17] LOG: could not rename temporary statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": No such file or directory
> That's a LOG level message, not an ERROR level message. Does Postgres not work?
>
>
--
Angular momentum makes the world go 'round.
