From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | roshan2013 <codevally(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Save postgresql node to catch only DML except delete queries |
Date: | 2013-05-01 17:30:48 |
Message-ID: | 87y5bytxo7.fsf@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
roshan2013 <codevally(at)gmail(dot)com> writes:
> Hi
>
> I want to keep one slave node along with our production master server, but
> that slave node only accept all the DML except Delete queries.
>
> Primary purpose of this slave node is to keep all the data inserted to the
> primary database and no need to delete any data from that.
>
> Anybody know how to achieve this by using postgresql in-built support or
> using any tool?
Suggest you research logical replication solution such as Slony or
SkyTools.
You wil need to implement your own row firing triggers on archiving
tables such that delets are a no-op.
> Thanks
>
> /Pradeep.
>
>
>
> --
> View this message in context: http://postgresql.1045698.n5.nabble.com/Save-postgresql-node-to-catch-only-DML-except-delete-queries-tp5753603.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2013-05-01 18:21:39 | Re: zLinux Load Testing Experience |
Previous Message | Steven Schlansker | 2013-05-01 16:48:56 | Re: Simple SQL INSERT to avoid duplication failed: why? |