Re: PostgreSQL Write Performance - Mailing list pgsql-general

From Dann Corbit
Subject Re: PostgreSQL Write Performance
Date
Msg-id D425483C2C5C9F49B5B7A41F89441547029626B6@postal.corporate.connx.com
Whole thread Raw
In response to Re: PostgreSQL Write Performance  (Yan Cheng Cheok <yccheok@yahoo.com>)
List pgsql-general
> -----Original Message-----
> From: Yan Cheng Cheok [mailto:yccheok@yahoo.com]
> Sent: Monday, January 04, 2010 11:30 PM
> To: Dann Corbit
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] PostgreSQL Write Performance
>
> >> What is the actual problem you are trying to solve?
>
> I am currently developing a database system for a high speed
> measurement machine.
>
> The time taken to perform measurement per unit is in term of ~30
> milliseconds. We need to record down the measurement result for every
> single unit. Hence, the time taken by record down the measurement
> result shall be far more less than milliseconds, so that it will have
> nearly 0 impact on the machine speed (If not, machine need to wait for
> database to finish writing, before performing measurement on next
unit)
>
> Previously, we are using flat file.. However, using flat file is quite
> a mess, when come to generating reports to customers.

Does the data volume build continuously so that the file becomes
arbitrarily large, or can you archive data that is more than X days old?
What is the format of a record?
What is the format of the incoming data?
Do you need indexes on these records?
Is the stream of incoming data continuous around the clock, or are there
periods when there is no incoming data?



pgsql-general by date:

Previous
From: Yan Cheng Cheok
Date:
Subject: Re: PostgreSQL Write Performance
Next
From: Greg Smith
Date:
Subject: Re: timestams in the the pg_standby output