From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | andrea suisani <suisani(at)demetra(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: 7.3.2 strange behavior (long) |
Date: | 2003-03-24 18:57:06 |
Message-ID: | 1048532226.13798.294.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, 2003-03-20 at 08:05, andrea suisani wrote:
> Hello,
>
> Firstly I apologise for my terrible english.
> we are using postgresql 7.2.x (currently 7.2.4)
> on our production server for last year (and also
> we are on suse 7.2).
>
> Last night i was working on the project for
> porting our application on pgsql 7.3.2 when a strange
> thing happen. The machine hangs (not only postgres) after
> I submit via psql this query "update coop_uni set msg_quote=''"
> to the server. The structure of this table is:
>
<snip>
>
> When i try to manually reboot the box
> I have another problem. the machine hangs during
> the boot with this message:
>
> "Unable to handle kernel paging request at virtual address dc7d00
> printing eip:
> c01ad272
> * pde = 17edb...
> ....
> Oops: 000
> CPU: 0
>
> ...."
>
<snip>
>
> The developing box is a "small" machine
> (celeron 1.2GHZ,ram 384MB, no scsi disks and
> PGDATA is on one ide disk), the kernel version
> is 2.4.20
>
> I wanted to ask to you if this problem can have had
> to a hardware issue or to something else.
>
I'm almost certain you have some kind of hardware issue, though
unfortunately I can't deduce just what it is. I'd start with checking
your ram, then maybe hdd. HTH.
Robert Treat
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-03-24 18:59:26 | Re: what its better seqscan or indexscan |
Previous Message | Robert Treat | 2003-03-24 18:51:08 | Re: ¿What's wrong? |