From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Hinse <loco@d0pefish.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: lseek
Date: Tue, 17 Feb 2009 16:34:44 -0500
Message-ID: <9125.1234906484@sss.pgh.pa.us> (raw)
In-Reply-To: <499B2423.3000809@d0pefish.de>
References: <499B2423.3000809@d0pefish.de>
Peter Hinse <loco@d0pefish.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, loco@d0pefish.de
Subject: Re: lseek
In-Reply-To: <9125.1234906484@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox