Re: [GENERAL] database is not accepting commands
От | Adrian Klaver |
---|---|
Тема | Re: [GENERAL] database is not accepting commands |
Дата | |
Msg-id | e3b11dce-f7a0-212f-ef06-c3d45df3353e@aklaver.com обсуждение исходный текст |
Ответ на | [GENERAL] database is not accepting commands (reem <dailyemailr@gmail.com>) |
Ответы |
Re: [GENERAL] database is not accepting commands
Re: [GENERAL] database is not accepting commands |
Список | pgsql-general |
On 05/16/2017 01:28 AM, reem wrote: > We have 1.5 TB database that's shown an error and block all commands. > The error is : > "ERROR: database is not accepting commands to avoid wraparound data loss in > database "dbname" > HINT: Stop the postmaster and use a standalone backend to vacuum that > database. > You might also need to commit or roll back old prepared transactions." > > I tried to do vacuum in the backend mode. Also I tried to set > zero_damaged_pages = on then do the vacuum again but same error appeared. > The error appeared after two hours of vacuuming where verbose shows passing > tables. Postgres version? So was all the above done in the standalone backend? > > The cause of error could be : > 1- a lot of insertion queries for not existing table > or > 2- truncating data with 40 GB in a week, > we used to do that but this is the first time we had this error. > also, autovacuume is turned on. > > Please , I need help or any suggestion? > > > > > > > -- > View this message in context: http://www.postgresql-archive.org/database-is-not-accepting-commands-tp5961831.html > Sent from the PostgreSQL - general mailing list archive at Nabble.com. > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: