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@xxxxxxxxxxxxxxx> wrote:
On 10 June 2016 at 18:56, John R Pierce <pierce@xxxxxxxxxxxx> 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.--
