Re: segfault when creating index on huge table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yiqing Jin <yiqing(dot)jin(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: segfault when creating index on huge table
Date: 2015-07-16 18:14:52
Message-ID: 4948.1437070492@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Yiqing Jin <yiqing(dot)jin(at)gmail(dot)com> writes:
> I'm trapped with a problem when trying to create an index on a table with
> about 2.8 billion records in it.
> ALTER TABLE ONLY nodes ADD CONSTRAINT pk_nodes PRIMARY KEY (id);
> or
> create index pknode on nodes(id);

> Postgres terminated with segfault during the proocess.

That shouldn't happen. Can you get a stack trace from the core dump?

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2015-07-16 18:16:07 Re: postgres_fdw user mapping and role inheritance
Previous Message Guillaume Lelarge 2015-07-16 18:11:50 Re: Automatic restore corruption problem