Re: [HACKERS] Online DW
| От | Sridhar N Bamandlapally |
|---|---|
| Тема | Re: [HACKERS] Online DW |
| Дата | |
| Msg-id | CAGuFTBVQs8nWj59VnES+aCeb+K6eQtpYJ+nwg3srkkZND3K2qQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Online DW (Craig Ringer <craig@2ndquadrant.com>) |
| Ответы |
Re: [HACKERS] Online DW
Re: [HACKERS] Online DW |
| Список | pgsql-general |
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
On 10 Jun 2016 19:03, "Craig Ringer" <craig@2ndquadrant.com> wrote:
On 10 June 2016 at 18:56, John R Pierce <pierce@hogranch.com> wrote:On 6/10/2016 2:18 AM, Sridhar N Bamandlapally wrote:This/These will be performed in Production to clean-up archive which will not be sync with Archive/DW DB only
one heads-up is Archive/DW DB may need to build WITHOUT CONSTRAINTS
May need to introduce ARCHIVE system/tag in pg_hba.conf
there's a whole lot of implied magic here unless you want to get way more specific what these features do, exactly, under all possible conditions.I'd go further than that and say I can't see how something like this could possibly work with physical (block based) replication. It's total hand-waving.--
В списке pgsql-general по дате отправления: