| From: | Tim Uckun <timuckun(at)gmail(dot)com> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)mail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Running update in chunks? |
| Date: | 2013-01-25 11:38:53 |
| Message-ID: | CAGuHJrMHd+EACfUzbUuhHZs=wQzNbiQYyTLMBi8yQ=JAW4wLHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> That suggests (to me, at least) that it is related to index updating. Again,
> your GIN index seems primary candidate.
>
> Try running iostat (I think that's available on a Mac) with/without the
> fillfactor and with/without the GIN index while you do the updates. It's
> possible your SSD is just behaving oddly under stress.
>
I dropped the index and the numbers shot up tenfold or more. I don't
know why postgres feels the need to update the GIN index on the hstore
field when I am only updating an integer field but it looks like I
need to split the hstore into a different table.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2013-01-25 11:46:49 | Re: seeking SQL book recommendation |
| Previous Message | Jan Strube | 2013-01-25 10:30:13 | Prevent out of memory errors by reducing work_mem? |