| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Torello Querci <tquerci(at)gmail(dot)com> |
| 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:26:18 |
| Message-ID: | 20130826162617.GA26610@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Torello Querci escribió:
> 2013/8/26 Luca Ferrari <fluca1978(at)infinito(dot)it>
>
> > On Mon, Aug 26, 2013 at 4:27 PM, Torello Querci <tquerci(at)gmail(dot)com> wrote:
> > > ERROR: unexpected end of tape
> >
> > Really strange, if I get it right something went wrong while sorting
> > tuples.
> > Is it possible to test with an incremented work_mem value?
> >
> > Actually I use the default work_set value (1MB).
> Of course it is possible increase work_set value to any values.
> Now I'll try with 10MB (shared_buffers is set to 412MB).
> If you think that 10MB is a very low value for a table with million of
> records I can try to increase work_set value to higher value.
Note that index creation uses maintenance_work_mem to limit memory used,
not work_mem.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Torello Querci | 2013-08-26 16:37:15 | Re: Problem creating index |
| Previous Message | Tom Lane | 2013-08-26 16:22:20 | Re: Problem creating index |