Re: [Non-DoD Source] Re: Database Error

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Ferrell, Denise D CTR NSWCDD, H11
Sent: Friday, October 27, 2017 9:35 AM
To: pgsql-admin
Subject: Re: [Non-DoD Source] Re: [ADMIN] Database Error
Importance: High

I've ran the vacuum freeze which corrected some issues but now I'm getting the following WARNING:

"terminating connection because of crash of another server process
"relation "<table_name>" page 1601779 is uninitialized --- fixing"

Is there something else that is needed besides the VACUUM FREEZE?

Thank you in advance,
Denise Ferrell

-----Original Message-----
From: Ferrell, Denise D CTR NSWCDD, H11
Sent: Wednesday, October 25, 2017 2:00 PM
To: 'Don Seiler'
Subject: RE: [Non-DoD Source] Re: [ADMIN] Database Error

Got it!

Is there a way to extent the max number for these?

d

-----Original Message-----
From: Don Seiler [mailto:don(at)seiler(dot)us]
Sent: Wednesday, October 25, 2017 12:32 PM
To: Ferrell, Denise D CTR NSWCDD, H11
Subject: Re: [Non-DoD Source] Re: [ADMIN] Database Error

Make sure you are using the FREEZE option. That is what resets the transaction IDs (which is the problem you're seeing).

On Wed, Oct 25, 2017 at 11:30 AM, Ferrell, Denise D CTR NSWCDD, H11 <denise(dot)ferrell(dot)ctr(at)navy(dot)mil> wrote:

Thank you again for the information. I'm currently in and running a full vacuum.

Denise

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org <mailto:pgsql-admin-owner(at)postgresql(dot)org> [mailto:pgsql-admin-owner(at)postgresql(dot)org <mailto:pgsql-admin-owner(at)postgresql(dot)org> ] On Behalf Of Don Seiler
Sent: Wednesday, October 25, 2017 10:42 AM
To: Ferrell, Denise D CTR NSWCDD, H11
Cc: pgsql-admin
Subject: [Non-DoD Source] Re: [ADMIN] Database Error


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 <https://blog.sentry.io/2015/07/23/transaction-id-wraparound-in-postgres.html>

--

Don Seiler
www.seiler.us

--

Don Seiler
www.seiler.us