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.