Re: PostgreSQL service terminated by query - Mailing list pgsql-general
| From | adrian.kitchingman@dse.vic.gov.au |
|---|---|
| Subject | Re: PostgreSQL service terminated by query |
| Date | |
| Msg-id | OF5FE6E87E.D3339CAD-ONCA257B3B.00044A64-CA257B3B.0004F9DC@LocalDomain Whole thread Raw |
| In response to | Re: PostgreSQL service terminated by query (Richard Huxton <dev@archonet.com>) |
| List | pgsql-general |
Thanks for the suggestion Richard.
I dumped the two tables in question and restored them which got the query working for a while until it eventually crashed the service again at another gid. I'll do a RAM check tonight.
I transferred the whole database to another computer and so far the query is working without issues.
Government men in black will be knocking on your door soon. ;-)
Cheers
Adrian
From: Richard Huxton <dev@archonet.com>
To: adrian.kitchingman@dse.vic.gov.au,
Cc: pgsql-general@postgresql.org
Date: 26/03/2013 10:32 PM
Subject: Re: [GENERAL] PostgreSQL service terminated by query
Sent by: pgsql-general-owner@postgresql.org
On 26/03/13 05:55, adrian.kitchingman@dse.vic.gov.au wrote:
> I'm hoping I can get some info on a query which terminates my PostgreSQL
> service.
> The query is a relatively simple PostGIS query:
> The log text when the service crashes is:
> 2013-03-26 15:49:55 EST LOG: server process (PID 3536) was terminated by
> exception 0xC0000005
> 2013-03-26 15:49:55 EST HINT: See C include file "ntstatus.h" for a
> description of the hexadecimal value.
> I'm running PostgreSQL 9.1 with PostGIS 2.0 installed on an WinXP SP3:
> 4GB RAM machine. Shared_buffers set at 50MB. Let me know if further info
> needed.
This is a Windows memory-related error. It might be due to a library
problem, bad RAM or a corrupted pointer in the database table itself.
1. Can you reliably produce the error with this specific gid?
2. Can you dump the database (or perhaps just the tables in question)?
If we can't find any problems in the database itself and you can spare
the downtime, it may be worth running a RAM checker overnight.
> Notice:
> This email and any attachments may contain information that is personal,
> confidential,
> legally privileged and/or copyright. No part of it should be reproduced,
> adapted or communicated without the prior written consent of the
> copyright owner.
Oh no, too late!
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I dumped the two tables in question and restored them which got the query working for a while until it eventually crashed the service again at another gid. I'll do a RAM check tonight.
I transferred the whole database to another computer and so far the query is working without issues.
Government men in black will be knocking on your door soon. ;-)
Cheers
Adrian
From: Richard Huxton <dev@archonet.com>
To: adrian.kitchingman@dse.vic.gov.au,
Cc: pgsql-general@postgresql.org
Date: 26/03/2013 10:32 PM
Subject: Re: [GENERAL] PostgreSQL service terminated by query
Sent by: pgsql-general-owner@postgresql.org
On 26/03/13 05:55, adrian.kitchingman@dse.vic.gov.au wrote:
> I'm hoping I can get some info on a query which terminates my PostgreSQL
> service.
> The query is a relatively simple PostGIS query:
> The log text when the service crashes is:
> 2013-03-26 15:49:55 EST LOG: server process (PID 3536) was terminated by
> exception 0xC0000005
> 2013-03-26 15:49:55 EST HINT: See C include file "ntstatus.h" for a
> description of the hexadecimal value.
> I'm running PostgreSQL 9.1 with PostGIS 2.0 installed on an WinXP SP3:
> 4GB RAM machine. Shared_buffers set at 50MB. Let me know if further info
> needed.
This is a Windows memory-related error. It might be due to a library
problem, bad RAM or a corrupted pointer in the database table itself.
1. Can you reliably produce the error with this specific gid?
2. Can you dump the database (or perhaps just the tables in question)?
If we can't find any problems in the database itself and you can spare
the downtime, it may be worth running a RAM checker overnight.
> Notice:
> This email and any attachments may contain information that is personal,
> confidential,
> legally privileged and/or copyright. No part of it should be reproduced,
> adapted or communicated without the prior written consent of the
> copyright owner.
Oh no, too late!
--
Richard Huxton
Archonet Ltd
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Notice:
This email and any attachments may contain information that is personal, confidential,
legally privileged and/or copyright. No part of it should be reproduced, adapted or communicated without the prior written consent of the copyright owner.
It is the responsibility of the recipient to check for and remove viruses.
If you have received this email in error, please notify the sender by return email, delete it from your system and destroy any copies. You are not authorised to use, communicate or rely on the information contained in this email.
Please consider the environment before printing this email.
pgsql-general by date: