| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Bernhard Ankenbrand <b(dot)ankenbrand(at)media-one(dot)de> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Crash in postgres/linux on verly large database |
| Date: | 2004-04-06 17:17:03 |
| Message-ID: | Pine.LNX.4.33.0404061115310.16211-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 6 Apr 2004, Bernhard Ankenbrand wrote:
> Hi,
>
> we have a table width about 60.000.000 entrys and about 4GB storage size.
> When creating an index on this table the whole linux box freezes and the
> reiser-fs file system is corrupted on not recoverable.
>
> Does anybody have experience with this amount of data in postgres 7.4.2?
> Is there a limit anywhere?
If your file system is getting corrupted, then you likely have found a bug
in reiserfs or the linux kernel. While some pgsql bug might be able to
corrupt the contents of a file belonging to it, it doesn't have the power
to corrupt the file system itself.
Or is the problem a corrupted database, not a corrupted file system?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bob | 2004-04-06 17:28:51 | Subqueries failing inside pl/pgsql fuction called by trigger |
| Previous Message | Ron St-Pierre | 2004-04-06 17:16:18 | Re: concat strings but spaces |