Re: Large index operation crashes postgres
От | Tom Lane |
---|---|
Тема | Re: Large index operation crashes postgres |
Дата | |
Msg-id | 28293.1269462412@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Large index operation crashes postgres (Frans Hals <fhals7@googlemail.com>) |
Ответы |
Re: Large index operation crashes postgres
|
Список | pgsql-general |
Frans Hals <fhals7@googlemail.com> writes: > Whenever I try to add the follwing index to the table "placex", one of > the postmaster processes dies and the server restarts. Can you provide a stack trace from the crash? > I try: > CREATE INDEX idx_placex_sector ON placex USING btree > (geometry_sector(geometry), rank_address, osm_type, osm_id); > The table counts around 50.000.000 rows. > The first 20.000.000 are indexed in 20-30 minutes. Nice! > Then indexing becomes slow and slower, first taking 100.000 rows in > ten minutes while further consequently decreasing speed. > When the job reaches something around row 25.000.000 postgres goes down: On what exactly do you base these statements about number of rows processed? CREATE INDEX doesn't provide any such feedback that I'm aware of. regards, tom lane
В списке pgsql-general по дате отправления: