| From: | Peter Hinse <loco(at)d0pefish(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: lseek |
| Date: | 2009-02-18 20:31:25 |
| Message-ID: | 499C701D.2010403@d0pefish.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tom Lane schrieb:
> 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.
Hi Tom,
thanks for your hints, I will check this with our R&D people. And yes:
with "huge" I meant the number of relations.
Regards,
Peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Monnerie | 2009-02-18 21:35:10 | Re: 8.3.5 broken after power fail |
| Previous Message | Isabella Ghiurea | 2009-02-18 19:05:28 | psqlrc cfg file |