| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | "Ferrell, Denise D CTR NSWCDD, H11" <denise(dot)ferrell(dot)ctr(at)navy(dot)mil> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Database Error |
| Date: | 2017-10-25 14:42:03 |
| Message-ID: | CAHJZqBBs3b8cKkH9qrcpWDJc2d+hqhdENWyjVMFbDShr5QpnBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Oct 25, 2017 at 7:30 AM, Ferrell, Denise D CTR NSWCDD, H11 <
denise(dot)ferrell(dot)ctr(at)navy(dot)mil> wrote:
> Using PostgreSQL v9.3 on RedHat platform.
>
> Last week the VM that the database resides on ran out of space...since
> that time after bringing the service back on-line getting intermittent
> connection issues.
>
> Today I'm receiving the following.
>
> ERROR: database is not accepting commands to avoid wraparound data loss
> in database "----"
> 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.
>
Sounds like you'll need to restart the DB in single-user mode and run a
VACUUM FREEZE on the whole thing.
Here's a good read on a similar incident:
https://blog.sentry.io/2015/07/23/transaction-id-wraparound-in-postgres.html
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2017-10-25 16:03:12 | Re: [Non-DoD Source] Re: Database Error |
| Previous Message | Gust, Thorsten | 2017-10-25 13:19:46 | Migrate from Oracle 12g to PostgreSQL 9.3 |