| From: | Ludwik Dylag <ldylag(at)gmail(dot)com> |
|---|---|
| To: | Nickolay <nitro(at)zhukcity(dot)ru> |
| Cc: | Pierre Frédéric Caillaud <lists(at)peufeu(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PG optimization question |
| Date: | 2010-01-09 18:58:22 |
| Message-ID: | 2fe468a21001091058q75074529p7674611926b9daa5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2010/1/9 Nickolay <nitro(at)zhukcity(dot)ru>
> Okay, I see your point with staging table. That's a good idea!
> The only problem I see here is the transfer-to-archive-table process. As
> you've correctly noticed, the system is kind of a real-time and there can be
> dozens of processes writing to the staging table, i cannot see how to make
> the transfer/flush process right and clear...
>
> The simplest way to do this is to create view and add/remove first/last day
by recreating the view on daily interval.
--
Ludwik Dyląg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-01-10 01:24:26 | Re: PG optimization question |
| Previous Message | Nickolay | 2010-01-09 18:50:07 | Re: PG optimization question |