| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Hinse <loco(at)d0pefish(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: lseek |
| Date: | 2009-02-17 21:34:44 |
| Message-ID: | 9125.1234906484@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Peter Hinse <loco(at)d0pefish(dot)de> writes:
> More info: the statement is an INSERT with some huge subselects, running
> every night on a PGSQL 8.3.6 on CentOS 4.7 x86_64. In 97% of all
> occasions, the job terminates in about 1-2 minutes - however, sometimes
> it just hangs. If terminated with kill <pid> and restarted, it always
> terminates.
Define "huge" --- you mean a lot of relations in the query? If you have
enough to trigger GEQO optimization, it could be that it's sometimes
picking a bad plan. You might try raising the geqo threshold to more
relations than that; or if this results in unacceptably long planning
time, increase geqo_effort instead.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Monnerie | 2009-02-17 22:55:15 | Re: 8.3.5 broken after power fail |
| Previous Message | DM | 2009-02-17 21:15:44 | Re: Pg 8.3.6 installation |