Re: Problem creating index

From: Torello Querci <tquerci(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Luca Ferrari <fluca1978(at)infinito(dot)it>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Problem creating index
Date: 2013-08-26 16:37:15
Message-ID: CA+igE6T55-bkgmxtUAQMfQbo8iM_qyBv7TdP0stbatmegzAJhA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2013/8/26 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

> Torello Querci <tquerci(at)gmail(dot)com> writes:
> > 2013/8/26 Luca Ferrari <fluca1978(at)infinito(dot)it>
> >> Is it possible to test with an incremented work_mem value?
>
> > Actually I use the default work_set value (1MB).
>
> maintenance_work_mem is what would be used for CREATE INDEX.
>
> Ok .... thanks

> FWIW, 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
message
psql:dump_ess_2013_08_26.sql:271177424: connection to server was lost

I was connected with psql -h localhost.

Any other suggestion?

Best Regards

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Janes 2013-08-26 16:53:43 Re: Is there any method to limit resource usage in PG?
Previous Message Alvaro Herrera 2013-08-26 16:26:18 Re: Problem creating index