Re: Using postgresql in situation with high write/read ratio

From: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
To: Odd Man <valodzka(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Using postgresql in situation with high write/read ratio
Date: 2010-08-12 20:26:07
Message-ID: AANLkTimU-+HrjwJReUtzxbrUq305vXXgCRwaanU-voqq@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On 13 August 2010 00:09, Odd Man <valodzka(at)gmail(dot)com> wrote:
> replaced with version two that uses partitions, truncate, copy and cleanup
> of old data once daily.

It makes me think that you have developed some rotation mechanism to
process incoming data. If so there is a batch-processing queue-based
solution called PgQ (start w/ it
http://wiki.postgresql.org/wiki/PGQ_Tutorial) The technology is
rather fast and smart IMHO.

--
Sergey Konoplev

Blog: http://gray-hemp.blogspot.com /
Linkedin: http://ru.linkedin.com/in/grayhemp /
JID/GTalk: gray(dot)ru(at)gmail(dot)com / Skype: gray-hemp / ICQ: 29353802

In response to

Browse pgsql-general by date

  From Date Subject
Next Message akp geek 2010-08-12 20:48:03 pg_toast_temp & pg_temp schemas
Previous Message Thom Brown 2010-08-12 20:17:00 Re: Using postgresql in situation with high write/read ratio