Re: [SQL] PostgreSQL server terminated by signal 11

> De : jeff(at)glacier(dot)frostconsultingllc(dot)com
> [mailto:jeff(at)glacier(dot)frostconsultingllc(dot)com] De la part de Jeff Frost
> Envoyé : jeudi, juillet 27, 2006 12:07
> À : Daniel Caune
> Cc : pgsql-sql(at)postgresql(dot)org; pgsql-admin(at)postgresql(dot)org
> Objet : Re: [SQL] PostgreSQL server terminated by signal 11
>
> On Thu, 27 Jul 2006, Daniel Caune wrote:
>
> > My PostgreSQL server running on a Linux machine is terminated by signal
> > 11 whenever I try to create some indexes on a table, which contains
> > quite a lot of data. However I succeeded in creating some other indexes
> > without having the PostgreSQL server terminated:
>
> Daniel,
>
> I would guess this is more appropriate for the -admin list so I cc'd it.
>
> I think you are most likely running out of memory or running up against a
> ulimit on memory. I would first check my ulimit settings on the postgres
> user
> and see if they are a bit small.
>

Actually ulimit is unlimited for user postgres and when the server was terminated the memory used was not that much compared to the machine capacity:

Mem: 2075860k total, 1663520k used, 412340k free, 5620k buffers
Swap: 369452k total, 0k used, 369452k free, 1626176k cached

I feel a bit lost, because it was running pretty well for the last couple months. This table is a data stage table where some data are imported in from OLTP databases, this every day. Indexes are dropped before inserting data and created when insertion has finished. The structure didn't change since a while.

Regards,

--
Daniel