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 12 Jun 2016, at 4:03, Christian Ohler wrote:
> we have a use case similar to auditing packages like pgMemento or Audit
> Trigger 91plus – we are looking to keep an ordered history of certain write
> transactions. I'm trying to understand the trade-offs between different ways
> of gettin
On 11 June 2016 at 02:26, David G. Johnston
wrote:
> On Fri, Jun 10, 2016 at 2:12 PM, Rakesh Kumar
> wrote:
>
>> Sorry if this question was asked before. As I understand currently
>> BDR does not support the replicating nodes to run different major
>> versions, like
>> 9.4 <-> 9.5.
>>
>> Is thi
On 11 June 2016 at 02:12, Rakesh Kumar wrote:
> Sorry if this question was asked before. As I understand currently
> BDR does not support the replicating nodes to run different major
> versions, like
> 9.4 <-> 9.5.
>
> Is this in the works?
>
Not with BDR between 9.4 and 9.5, no, as there will
Christian Ohler writes:
> we have a use case similar to auditing packages like pgMemento or Audit
> Trigger 91plus â we are looking to keep an ordered history of certain write
> transactions. I'm trying to understand the trade-offs between different
> ways of getting that order, i.e., assigning
Hi guys,
In the db I'm working one, it will be three tables:
visits, work, others.
Everything the customer do, will be logged. All inserts/updates/deletes
will be logged.
Option 1: Each table would have its own log table.
visits_logs, work_logs, others_logs
Option 2: All the logs would be stor
Also...
if something is changed inside the visits table (delete/insert/update), the
visits_logs table will be logging the change.
However, some joins between those three tables will become necessary in
some point, as visits and works tables are related somehow...
Hi all,
I am looking for some pg_tune replacement, which is working for latest
PostgreSQL versions. What I need is to have some tool, which can compute
some basic, reasonable configuration defaults for basic deployment
scenarios like pg_tune did - dedicated server, web server ...
I understand, tha
