Postgres Pro
Downloads
Home   >   mailing lists

Thread: BUG #9333: The PostgreSQL service stops unexpectedly

BUG #9333: The PostgreSQL service stops unexpectedly

From
cyriacmaliyil@gmail.com
Date:
The following bug has been logged on the website:

Bug reference:      9333
Logged by:          cyriac Joseph
Email address:      cyriacmaliyil@gmail.com
PostgreSQL version: 9.2.0
Operating system:   Windows XP SP3
Description:

The PostgreSQL service stops unexpectedly, and needs to be restarted. It is
a very crucial situation when all the client systems to be restarted. Mostly
this happens in the middle of a data entry and all the entered data is lost.

Re: BUG #9333: The PostgreSQL service stops unexpectedly

From
John R Pierce
Date:
On 2/24/2014 2:20 AM, cyriacmaliyil@gmail.com wrote:
> The PostgreSQL service stops unexpectedly, and needs to be restarted. It is
> a very crucial situation when all the client systems to be restarted. Mostly
> this happens in the middle of a data entry and all the entered data is lost.


A)  9.2.0 is an old release, it should be updated to 9.2.7 (this update
should just require restarting postgres)

B)  I'd look in postgres' logfiles, likely in the pg_log subdirectory
under the data directory, to see what event caused this crash.

[please relpy to pgsql-bugs@postgresql.org, not me directly]

Re: BUG #9333: The PostgreSQL service stops unexpectedly

From
Cyriac Joseph Maliyil
Date:

Dear Mr. John R Pierce  

As per your mail I am attaching the log files herewith.

Kindly inspect the same and give your valuable advice.

Regards,
Cyriac Joseph Maliyil



On Tue, Feb 25, 2014 at 2:03 AM, John R Pierce <pierce@hogranch.com> wrote:
On 2/24/2014 2:20 AM, cyriacmaliyil@gmail.com wrote:
The PostgreSQL service stops unexpectedly, and needs to be restarted. It is
a very crucial situation when all the client systems to be restarted. Mostly
this happens in the middle of a data entry and all the entered data is lost.


A)  9.2.0 is an old release, it should be updated to 9.2.7 (this update should just require restarting postgres)

B)  I'd look in postgres' logfiles, likely in the pg_log subdirectory under the data directory, to see what event caused this crash.

[please relpy to pgsql-bugs@postgresql.org, not me directly]




--
Cyriac Joseph Maliyil

Attachment