From: | David Ford <david(at)blue-labs(dot)org> |
---|---|
To: | Bruce Irvine <b(dot)irvine(at)sportingpulse(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: URGENT PROBLEM |
Date: | 2001-06-06 00:08:08 |
Message-ID: | 3B1D7468.8060706@blue-labs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
How 'bout posting what version of pgsql you're running, and we'll start
back at square one :)
-d
Bruce Irvine wrote:
> Hi All,
>
>
>
> This is my first post, so I hope I'm in the right area and doing it
> correctly.
>
>
>
> We are having MAJOR & URGENT problems with Postresql occaisonly
> corrupting tables on insert. I had a quick look through your archive
> and couldn't find anything. It seems to happen mostly on large inserts
> (lots of data into one text field). This results in corrupting the
> table and hanging the psql console whenever I try to INSERT, UPDATE,
> DELETE, SELECT, etc. Doing an "EXPLAIN SELECT * FROM table" shows that
> I have around 100 - 1000 extra rows. The problem is often fixed by
> running VACUUM against the table, however VACUUM often hangs leaving
> the table locked until I delete the lock file.
>
>
>
> Its only a basic INSERT statement into a basic table.
>
>
>
> Thanks in advance.
>
>
>
> Bruce Irvine.
>
> SportingPulse.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-06 00:09:53 | Re: URGENT PROBLEM |
Previous Message | Tom Lane | 2001-06-06 00:03:24 | Re: Australian timezone configure option |