pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedERROR:::::: could not rename temporary statistics file ...
9+ messages / 3 participants
[nested] [flat]
* ERROR:::::: could not rename temporary statistics file ...
@ 2019-06-03 09:46 soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
0 siblings, 1 reply; 9+ messages in thread
From: soumik.bhattacharjee@kpn.com @ 2019-06-03 09:46 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
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
Thanks
Soumik
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
@ 2019-06-03 11:24 ` Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
0 siblings, 1 reply; 9+ messages in thread
From: Ron @ 2019-06-03 11:24 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com 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.
^ permalink raw reply [nested|flat] 9+ messages in thread
* RE: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
@ 2019-06-03 11:26 ` soumik.bhattacharjee@kpn.com
2019-06-03 11:32 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
0 siblings, 1 reply; 9+ messages in thread
From: soumik.bhattacharjee@kpn.com @ 2019-06-03 11:26 UTC (permalink / raw)
To: ronljohnsonjr@gmail.com; pgsql-admin@lists.postgresql.org
My pg_restore is stuck here for last 2 days.
pg_restore: creating CONSTRAINT "schema_name.num_servicenummer_historie snh_prx"
-----Original Message-----
From: Ron <ronljohnsonjr@gmail.com>
Sent: Monday, June 03, 2019 1:24 PM
To: pgsql-admin@lists.postgresql.org
Subject: Re: ERROR:::::: could not rename temporary statistics file ...
On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com 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.
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
@ 2019-06-03 11:32 ` Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:45 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 12:24 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 13:31 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-06 08:57 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
0 siblings, 4 replies; 9+ messages in thread
From: Ron @ 2019-06-03 11:32 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Please don't top-post.
On 6/3/19 6:26 AM, soumik.bhattacharjee@kpn.com 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?
> -----Original Message-----
> From: Ron <ronljohnsonjr@gmail.com>
> Sent: Monday, June 03, 2019 1:24 PM
> To: pgsql-admin@lists.postgresql.org
> Subject: Re: ERROR:::::: could not rename temporary statistics file ...
>
> On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com 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.
^ permalink raw reply [nested|flat] 9+ messages in thread
* RE: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:32 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
@ 2019-06-03 11:45 ` soumik.bhattacharjee@kpn.com
3 siblings, 0 replies; 9+ messages in thread
From: soumik.bhattacharjee@kpn.com @ 2019-06-03 11:45 UTC (permalink / raw)
To: ronljohnsonjr@gmail.com; pgsql-admin@lists.postgresql.org
Please don't top-post.
On 6/3/19 6:26 AM, soumik.bhattacharjee@kpn.com 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
> -----Original Message-----
> From: Ron <ronljohnsonjr@gmail.com>
> Sent: Monday, June 03, 2019 1:24 PM
> To: pgsql-admin@lists.postgresql.org
> Subject: Re: ERROR:::::: could not rename temporary statistics file ...
>
> On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com 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.
^ permalink raw reply [nested|flat] 9+ messages in thread
* RE: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:32 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
@ 2019-06-03 12:24 ` soumik.bhattacharjee@kpn.com
3 siblings, 0 replies; 9+ messages in thread
From: soumik.bhattacharjee@kpn.com @ 2019-06-03 12:24 UTC (permalink / raw)
To: ronljohnsonjr@gmail.com; pgsql-admin@lists.postgresql.org
Please don't top-post.
On 6/3/19 6:26 AM, soumik.bhattacharjee@kpn.com 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@gmail.com>
> Sent: Monday, June 03, 2019 1:24 PM
> To: pgsql-admin@lists.postgresql.org
> Subject: Re: ERROR:::::: could not rename temporary statistics file ...
>
> On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com 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.
^ permalink raw reply [nested|flat] 9+ messages in thread
* RE: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:32 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
@ 2019-06-03 13:31 ` soumik.bhattacharjee@kpn.com
3 siblings, 0 replies; 9+ messages in thread
From: soumik.bhattacharjee@kpn.com @ 2019-06-03 13:31 UTC (permalink / raw)
To: ronljohnsonjr@gmail.com; pgsql-admin@lists.postgresql.org
Hello Ron/All,
Please let me know if there is any performance improvements needed fort this restore? Its stuck here for last 2 days
On 6/3/19 6:26 AM, soumik.bhattacharjee@kpn.com<mailto:soumik.bhattacharjee@kpn.com> 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$
Its mainly struck here - pg_restore: creating CONSTRAINT "schema_name.num_servicenummer_historie snh_prx"
Thanks
Soumik
> -----Original Message-----
> From: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>
> Sent: Monday, June 03, 2019 1:24 PM
> To: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
> Subject: Re: ERROR:::::: could not rename temporary statistics file ...
>
> On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com<mailto:soumik.bhattacharjee@kpn.com> 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.
^ permalink raw reply [nested|flat] 9+ messages in thread
* RE: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:32 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
@ 2019-06-06 08:57 ` soumik.bhattacharjee@kpn.com
2019-06-06 14:34 ` Re: ERROR:::::: could not rename temporary statistics file ... Laurenz Albe <laurenz.albe@cybertec.at>
3 siblings, 1 reply; 9+ messages in thread
From: soumik.bhattacharjee@kpn.com @ 2019-06-06 08:57 UTC (permalink / raw)
To: ronljohnsonjr@gmail.com; pgsql-admin@lists.postgresql.org
Hello Experts,
Any pointers fort this?
Thanks
From: Bhattacharjee, Soumik
Sent: Monday, June 03, 2019 3:32 PM
To: 'Ron' <ronljohnsonjr@gmail.com>; 'pgsql-admin@lists.postgresql.org' <pgsql-admin@lists.postgresql.org>
Subject: RE: ERROR:::::: could not rename temporary statistics file ...
Hello Ron/All,
Please let me know if there is any performance improvements needed fort this restore? Its stuck here for last 2 days
On 6/3/19 6:26 AM, soumik.bhattacharjee@kpn.com<mailto:soumik.bhattacharjee@kpn.com> 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$
Its mainly struck here - pg_restore: creating CONSTRAINT "schema_name.num_servicenummer_historie snh_prx"
Thanks
Soumik
> -----Original Message-----
> From: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>
> Sent: Monday, June 03, 2019 1:24 PM
> To: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
> Subject: Re: ERROR:::::: could not rename temporary statistics file ...
>
> On 6/3/19 4:46 AM, soumik.bhattacharjee@kpn.com<mailto:soumik.bhattacharjee@kpn.com> 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.
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: ERROR:::::: could not rename temporary statistics file ...
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:32 ` Re: ERROR:::::: could not rename temporary statistics file ... Ron <ronljohnsonjr@gmail.com>
2019-06-06 08:57 ` RE: ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
@ 2019-06-06 14:34 ` Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 0 replies; 9+ messages in thread
From: Laurenz Albe @ 2019-06-06 14:34 UTC (permalink / raw)
To: soumik.bhattacharjee@kpn.com; ronljohnsonjr@gmail.com; pgsql-admin@lists.postgresql.org
soumik.bhattacharjee@kpn.com wrote:
> Please let me know if there is any performance improvements needed fort this restore? Its stuck here for last 2 days
>
> > 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
90% I/O-wait looks like the I/O subsystem has a problem.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
^ permalink raw reply [nested|flat] 9+ messages in thread
end of thread, other threads:[~2019-06-06 14:34 UTC | newest]
Thread overview: 9+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-06-03 09:46 ERROR:::::: could not rename temporary statistics file ... soumik.bhattacharjee@kpn.com
2019-06-03 11:24 ` Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:26 ` soumik.bhattacharjee@kpn.com
2019-06-03 11:32 ` Ron <ronljohnsonjr@gmail.com>
2019-06-03 11:45 ` soumik.bhattacharjee@kpn.com
2019-06-03 12:24 ` soumik.bhattacharjee@kpn.com
2019-06-03 13:31 ` soumik.bhattacharjee@kpn.com
2019-06-06 08:57 ` soumik.bhattacharjee@kpn.com
2019-06-06 14:34 ` Laurenz Albe <laurenz.albe@cybertec.at>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox