X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 82AB0474E4F for ; Fri, 21 Feb 2003 03:04:51 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 39084-05 for ; Fri, 21 Feb 2003 03:04:40 -0500 (EST) Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id D5742474E61 for ; Fri, 21 Feb 2003 03:04:36 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h1L84aA55003 for pgsql-performance@postgresql.org; Fri, 21 Feb 2003 16:04:36 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Received: from mariner (mariner.internal [192.168.0.101]) by houston.familyhealth.com.au (8.11.6/8.9.3) with SMTP id h1L84X754913; Fri, 21 Feb 2003 16:04:33 +0800 (WST) Message-ID: <0a6901c2d97f$ea1369d0$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: "Jakab Laszlo" , References: <004501c2d97d$98927670$0900000a@new> Subject: Re: performance issues for processing more then 150000 records / day. Date: Fri, 21 Feb 2003 16:04:52 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0A66_01C2D9C2.F8169EB0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-scanner: scanned by Inflex 0.1.5c - (http://www.inflex.co.za/) X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/144 X-Sequence-Number: 1200 This is a multi-part message in MIME format. ------=_NextPart_000_0A66_01C2D9C2.F8169EB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Jakab, I don't see why postgresql wouldn't be able to handle that - it's a relativ= ely small amount of data. When you say 150000 records/day, do you mean: 1. 150000 inserts/day (ie. database grows constantly, quickly) 2. 150000 updates/deletes/day 3. 150000 transactions/select/day If you give us a little more information, we'll be able to help you tune yo= ur postgres for your application. Regards, Chris ----- Original Message -----=20 From: Jakab Laszlo=20 To: pgsql-performance@postgresql.org=20 Sent: Friday, February 21, 2003 3:48 PM Subject: [PERFORM] performance issues for processing more then 150000 rec= ords / day. Hello, We would like to use PostgreSQL for one project. This project would need to handle some of 150000 - 200000 (thousands reco= rds) per day. Is there somebody having experience with Postgresql in this kind of envir= onment. Can anybody advice us regarding specific PostgreSQL issues for such kind = of datamanipulation ? Best Regards, Jaki ------=_NextPart_000_0A66_01C2D9C2.F8169EB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Jakab,
 
I don't see why postgresql wouldn't be abl= e to=20 handle that - it's a relatively small amount of data.
 
When you say 150000 records/day, do you=20 mean:
 
1. 150000 inserts/day (ie. database grows= =20 constantly, quickly)
2. 150000 updates/deletes/day
3. 150000 transactions/select/day
 
If you give us a little more information, = we'll be=20 able to help you tune your postgres for your application.
 
Regards,
 
Chris
 
----- Original Message -----
Fro= m:=20 Jakab=20 Laszlo
To: pgsql-performance@postgr= esql.org=20
Sent: Friday, February 21, 2003 3:= 48=20 PM
Subject: [PERFORM] performance iss= ues for=20 processing more then 150000 records / day.

Hello,
 
We would like to use PostgreSQL for one= =20 project.
This project would need to handle some o= f 150000=20 - 200000 (thousands records) per day.
 
Is there somebody having experience with= =20 Postgresql in this kind of environment.
Can anybody advice us regarding specific= =20 PostgreSQL issues for such kind of datamanipulation ?
 
Best Regards,
Jaki
------=_NextPart_000_0A66_01C2D9C2.F8169EB0--