pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Jewell <c.jewell@lancaster.ac.uk>
To: pgsql-admin@postgresql.org
Subject: Re: Monitoring database for changes - backup purposes
Date: Fri, 14 Oct 2005 19:29:31 +0100
Message-ID: <434FF90B.4060902@lancaster.ac.uk> (raw)
In-Reply-To: <200510141059.39852.darcy@wavefire.com>
References: <434FB046.5070207@lancaster.ac.uk>
	<200510141059.39852.darcy@wavefire.com>

Hi,

Yes, diff would work and is my current plan, but it requires me to 
perform the backup first.  What I needed really was a system by which a 
backup would only be run if there was something that needed backing up.

Thanks anyway,

Chris

--
Chris Jewell, BSc(Hons), BVSc, MRCVS
Dept of Maths and Statistics
Fylde College
Lancaster University
Lancaster
Lancs
LA1 4YF 



Darcy Buskermolen wrote:

>On Friday 14 October 2005 06:19, Chris Jewell wrote:
>  
>
>>Hi,
>>
>>I have a query about a backup policy that I wish to implement.
>>Currently, we are running a PostgreSQL server with a very large database
>>on it.  The database consists of a core of read-only tables, with tables
>>created by the users going by default into the user's own schemas.  For
>>backup purposes, I have a script that uses pg_dump to create dumps of
>>the individual user schemas.  However, this is mainly a read-only
>>database and information is added or updated only rarely.  What I really
>>need is a method of monitoring the database, such that my backup script
>>will only back any one schema up if it has changed since it was last
>>backed up.  Is there any way to do this?  Is there a checksum function
>>or something that I could use?
>>    
>>
>
>No there is not, but would a diff -q be sufficient for your needs ?
>
>
>  
>
>>Thanks,
>>
>>Chris
>>    
>>
>
>  
>



view thread (5+ messages)  latest in thread

Message-ID: <434FF90B.4060902@lancaster.ac.uk>
Permalink:  ../434FF90B.4060902@lancaster.ac.uk/
Also on:    postgresql.org/message-id/434FF90B.4060902@lancaster.ac.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: c.jewell@lancaster.ac.uk
  Subject: Re: Monitoring database for changes - backup purposes
  In-Reply-To: <434FF90B.4060902@lancaster.ac.uk>
  References: <434FB046.5070207@lancaster.ac.uk> <200510141059.39852.darcy@wavefire.com> <434FF90B.4060902@lancaster.ac.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox