| From: | Devrim GUNDUZ <devrim(at)gunduz(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Mailing Lists-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Weird problem in 8.0.0 |
| Date: | 2005-01-24 16:45:17 |
| Message-ID: | Pine.LNX.4.61.0501241840310.32758@emo.org.tr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Mon, 24 Jan 2005, Tom Lane wrote:
>> I've changed statement_timeout value from 5 to 0; restarted PostgreSQL and
>> all commands are running now... So, what could be the problem with
>> statement_timeout?
>
> Apparently you need a timeout longer than 5 milliseconds.
>
> Note that the first few queries executed by a backend will take longer
> than "usual" because of the overhead of populating the catalog caches.
What I'm confused was "miliseconds", I saw it as "seconds" :)
Anyway, thanks.
- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFB9SYgtl86P3SPfQ4RAiAIAJ9aXeD9lTZKQKpjKdtvmp+Mczi16ACeNbYW
jtBVhUuI18xw8pF7RGKR1sE=
=iuHJ
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jarkko Elfving | 2005-01-24 16:46:25 | Re: Ident authentication SOLVED |
| Previous Message | Devrim GUNDUZ | 2005-01-24 16:43:46 | Re: Postgres 8.0 on RHEL |