Re: Problem creating index
От | Torello Querci |
---|---|
Тема | Re: Problem creating index |
Дата | |
Msg-id | CA+igE6SpffZmP3DAyYUaBUjDNwO2BqZfohWEqAzAgHmQvjQqjw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Problem creating index (Torello Querci <tquerci@gmail.com>) |
Ответы |
Re: Problem creating index
|
Список | pgsql-general |
Ok,
now create index is finished using maintenance_work_mem=100MB.
Thanks to all.
I suppose that an error message more clear can help.
Best Regards, Torello
2013/8/26 Torello Querci <tquerci@gmail.com>
2013/8/26 Tom Lane <tgl@sss.pgh.pa.us>Torello Querci <tquerci@gmail.com> writes:> 2013/8/26 Luca Ferrari <fluca1978@infinito.it>maintenance_work_mem is what would be used for CREATE INDEX.
>> Is it possible to test with an incremented work_mem value?
> Actually I use the default work_set value (1MB).Ok .... thanksFWIW, though, the combination of this weird error and the fact that you
had a corrupt index to begin with makes me suspicious that there's some
low-level problem. You might be well advised to do some memory testing
on that machine, for example.I check for ecc memory but unfortunally the machine use non ecc memory.This machine is installed on a remote site so I should to try to use e memory tester in normal linux shell, so I can't use memtest at boot level.In this moment I get this error while executing the restore of the big table in a different database on the same machine:psql:dump_ess_2013_08_26.sql:271177424: SSL error: sslv3 alert unexpected messagepsql:dump_ess_2013_08_26.sql:271177424: connection to server was lostI was connected with psql -h localhost.Any other suggestion?Best Regards
В списке pgsql-general по дате отправления: