| From: | Dan Wierenga <dwierenga(at)gmail(dot)com> |
|---|---|
| To: | Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Online DW |
| Date: | 2016-06-10 16:43:29 |
| Message-ID: | 1F383D47-EC87-45BF-AED4-1BF7FAAB6D01@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> On Jun 10, 2016, at 9:27 AM, Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> wrote:
>
> This is what I feel will give me solution to maintain production (current+7days) and archive(current+history) without any etl/scheduler
>
> But there is no feature available in any database
>
> Sridhar
> Opentext
>
If that's what you want, in any database, then MySQL's "SET sql_log_bin" statement could probably be used to accomplish what you want.
But, the engineering effort needed to get streaming replication to populate your data warehouse is probably much higher than just building an ETL job. Are you so certain your situation is so special that you can't use what the rest of the industry uses?
-Dan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-06-10 16:46:29 | Re: What is the general opinion on use of tablespaces |
| Previous Message | Sridhar N Bamandlapally | 2016-06-10 16:33:31 | Re: [HACKERS] Online DW |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2016-06-10 16:49:41 | Re: [HACKERS] Online DW |
| Previous Message | Sridhar N Bamandlapally | 2016-06-10 16:33:31 | Re: [HACKERS] Online DW |