On Sat, 11 Jun 2016 09:59:59 +0530
Sridhar N Bamandlapally wrote:
> Ok, let me put this way,
>
> I need every transaction coming from application sync with both
> production and archive db,
> but the transactions I do to clean old data(before 7 days) on
> production db in daily maintenance windo
On 11 June 2016 at 12:29, Sridhar N Bamandlapally
wrote:
> Ok, let me put this way,
>
> I need every transaction coming from application sync with both production
> and archive db,
> but the transactions I do to clean old data(before 7 days) on production
> db in daily maintenance window should n
On Sat, 11 Jun 2016 09:59:59 +0530
Sridhar N Bamandlapally wrote:
> Ok, let me put this way,
>
> I need every transaction coming from application sync with both
> production and archive db,
> but the transactions I do to clean old data(before 7 days) on
> production db in daily maintenance windo
Ok, let me put this way,
I need every transaction coming from application sync with both production
and archive db,
but the transactions I do to clean old data(before 7 days) on production db
in daily maintenance window should not sync with archive db,
Archive db need read-only, used for maintain
> On Jun 10, 2016, at 9:27 AM, Sridhar N Bamandlapally
> 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
On Fri, Jun 10, 2016 at 4:11 AM, Sridhar N Bamandlapally <
sridhar@gmail.com> wrote:
> Hi
>
> Is there any feature in PostgreSQL where online DW (Dataware housing) is
> possible ?
>
> am looking for scenario like
>
> 1. Production DB will have CURRENT + LAST 7 DAYS data only
>
> 2. Archive/DW
On Fri, Jun 10, 2016 at 12:49 PM, Francisco Olarte
wrote:
> I may be wrong but ...
>
> On Fri, Jun 10, 2016 at 6:33 PM, Sridhar N Bamandlapally
> wrote:
> > One thing we can restrict to "begin noarchive" transaction block are
> DELETE
> > and SELECT only
> > On 10 Jun 2016 21:57, "Sridhar N Bama
I may be wrong but ...
On Fri, Jun 10, 2016 at 6:33 PM, Sridhar N Bamandlapally
wrote:
> One thing we can restrict to "begin noarchive" transaction block are DELETE
> and SELECT only
> On 10 Jun 2016 21:57, "Sridhar N Bamandlapally"
> wrote:
>> This is what I feel will give me solution to mainta
One thing we can restrict to "begin noarchive" transaction block are DELETE
and SELECT only
Sridhar
Opentext
On 10 Jun 2016 21:57, "Sridhar N Bamandlapally"
wrote:
> This is what I feel will give me solution to maintain production
> (current+7days) and archive(current+history) without any etl/sc
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" wrote:
> On 10 June 2016 at 18:56, John R Pierce wrote
On 10 June 2016 at 18:56, John R Pierce 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
>>
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
One thing looks possible ( feature not available), just an idea
example/syntax:
BEGIN NOARCHIVE;
--- transaction-1
--- transaction-2
.
.
--- transaction-N
END;
This/These will be performed in Production to clean-up archive which will
not be sync with Archive/DW DB only
one heads-up
On 10 June 2016 at 16:11, Sridhar N Bamandlapally
wrote:
> Hi
>
> Is there any feature in PostgreSQL where online DW (Dataware housing) is
> possible ?
>
> am looking for scenario like
>
> 1. Production DB will have CURRENT + LAST 7 DAYS data only
>
> 2. Archive/DW DB will have CURRENT + COMPLETE
14 matches
Mail list logo
