From pgsql-admin@carladata.de Tue May 23 09:08:04 2006 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id BBDCD9FA1F1 for ; Tue, 23 May 2006 06:08:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 34922-03 for ; Tue, 23 May 2006 06:07:55 -0300 (ADT) X-Greylist: delayed 00:28:05.79492 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id A882A9F9CAA for ; Tue, 23 May 2006 06:07:55 -0300 (ADT) Received: from smtp1.mk-netzdienste.de (mail1.mk-netzdienste.de [213.172.96.165]) by svr4.postgresql.org (Postfix) with ESMTP id 9A9AE5B1DC3 for ; Tue, 23 May 2006 08:39:15 +0000 (GMT) Received: from localhost (scanner1.mk-netzdienste.de [213.172.96.174]) by smtpout.mk-netzdienste.de (Postfix) with ESMTP id 703743F7FC for ; Tue, 23 May 2006 10:39:12 +0200 (CEST) Received: from smtp1.mk-netzdienste.de ([213.172.96.165]) by localhost (scanner1.mk-netzdienste.de [213.172.96.174]) (amavisd-new, port 10024) with LMTP id 30365-02-55 for ; Tue, 23 May 2006 10:39:09 +0200 (CEST) Received: from geisslinger (unknown [213.172.114.97]) by smtp1.mk-netzdienste.de (Postfix) with SMTP id B8DF23F7AA for ; Tue, 23 May 2006 10:39:09 +0200 (CEST) Message-ID: <001301c67e44$6526df00$340aa8c0@geisslinger> From: "MG" To: Subject: sql-statement blocks maschine Date: Tue, 23 May 2006 10:39:24 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C67E55.289A2B30" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: by MK Netzdienste X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/310 X-Sequence-Number: 21842 This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C67E55.289A2B30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, we are using PostgreSQL 8.0.3 under SuSE Linux 9.2 and SCO OpenServer = 6.0 and have some perfomance problems. We are working with = telnet-clients, which controlls our application on the server. The = application does the sql-statements If we have sql-statements e.g. SELECT or UPDATE which takes some minutes = to be executed, then this statement blocks the whole maschine. This has = the affect, that the telnet-clients work very very slowly, e.g. it takes = several seconds from one keystroke to the next one. So you can`t work = with the application in a reasonable way. These sql-statments are so variable, that we can`t create a index for = each combination. How can we solve that problem? Greeting Michaela ------=_NextPart_000_0010_01C67E55.289A2B30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
we are using PostgreSQL 8.0.3 under SuSE Linux 9.2 and = SCO=20 OpenServer 6.0 and have some perfomance problems. We are working = with=20 telnet-clients, which controlls our application on the server. The = application=20 does the sql-statements
 
If we have sql-statements e.g. SELECT or UPDATE which takes = some=20 minutes to be executed, then this statement blocks the whole maschine. = This has=20 the affect, that the telnet-clients work very very slowly, e.g. it=20 takes several seconds from one keystroke to the next one. So you = can`t work=20 with the application in a reasonable way.
 
These sql-statments are so variable, that we can`t create a index = for each=20 combination.
 
How can we solve that problem?
 
Greeting
Michaela
------=_NextPart_000_0010_01C67E55.289A2B30-- From adamr@informatyka.gdansk.pl Tue May 23 11:46:49 2006 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id C82779F94EA for ; Tue, 23 May 2006 08:46:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 55559-04 for ; Tue, 23 May 2006 08:46:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ns1.peker.com.pl (181-ego-2.acn.waw.pl [62.121.85.181]) by postgresql.org (Postfix) with SMTP id B83D79F946D for ; Tue, 23 May 2006 08:46:41 -0300 (ADT) Received: (qmail 8776 invoked by uid 540); 23 May 2006 11:56:36 -0000 Received: from 153.19.179.26 by ns1.peker.com.pl (envelope-from , uid 401) with qmail-scanner-1.25st (clamdscan: 0.82/760. spamassassin: 3.0.2. perlscan: 1.25st. Clear:RC:1(153.19.179.26):. Processed in 0.071195 secs); 23 May 2006 11:56:36 -0000 Received: from rzgw.artnet.pl (HELO ?10.4.128.107?) (informatyka-adamr@153.19.179.26) by ns1.peker.com.pl with SMTP; 23 May 2006 11:56:35 -0000 Message-ID: <4472F5F1.1090803@informatyka.gdansk.pl> Date: Tue, 23 May 2006 13:45:53 +0200 From: Adam Radlowski User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: MG , pgsql-admin@postgresql.org Subject: Re: sql-statement blocks maschine References: <001301c67e44$6526df00$340aa8c0@geisslinger> In-Reply-To: <001301c67e44$6526df00$340aa8c0@geisslinger> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/312 X-Sequence-Number: 21844 Run the "top" program. You'll see, that Your server CPU time is strongly take by postmaster. The best way is to have two machines - servers: for database server and for terminals. Maybe good will be to have more than one CPU in the one server and run database server on CPU not used by others apps. Greetins Adam MG wrote: > Hello, > > we are using PostgreSQL 8.0.3 under SuSE Linux 9.2 and SCO OpenServer > 6.0 and have some perfomance problems. We are working with > telnet-clients, which controlls our application on the server. The > application does the sql-statements > > If we have sql-statements e.g. SELECT or UPDATE which takes some > minutes to be executed, then this statement blocks the whole maschine. > This has the affect, that the telnet-clients work very very slowly, > e.g. it takes several seconds from one keystroke to the next one. So > you can`t work with the application in a reasonable way. > > These sql-statments are so variable, that we can`t create a index for > each combination. > > How can we solve that problem? > > Greeting > Michaela