On 11/21/2014 07:38 PM, zach cruise wrote:
On 11/20/14, Adrian Klaver wrote:
On 11/20/2014 04:57 PM, zach cruise wrote:
On 11/20/14, Adrian Klaver wrote:
On 11/20/2014 12:30 PM, zach cruise wrote:
For more info see:
http://www.postgresql.org/docs/9.3/interactive/continuous-archiving.html
Thanks Laurenz, very good point!
Luckily (phew!) the business scenario is such that race conditions cannot
occur (and the transaction table is append only). There is business
workflow to address duplicates but
1) it occurs extremely rarely (it would be a deliberate sabotage if it
occurs)
2) there
