Skip site navigation (1) Skip section navigation (2)

Re: Schema unique stamp (OID, MD5?)

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>,pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Schema unique stamp (OID, MD5?)
Date: 2002-02-23 20:53:09
Message-ID: FED2B709E3270E4B903EB0175A49BCB10475EC@dogbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr] 
> Sent: 23 February 2002 19:59
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Schema unique stamp (OID, MD5?)
> 
> 
> Dear friends,
> 
> Do you see an existing way to stamp an existing schema with a 
> unique value 
> (OID?). This would be very usefull for pgAdmin2 when working 
> in development 
> teams to decide whether a schema should be reloaded or not.
> 
> Using PLbash, this would look like :
> "md5sum < pg_dump --schema-only database_name"
> Are there plans to implement such a feature server-side in C++? 

This would be very expensive, even on moderately sized databases wouldn't
it? Why not just check the ctid of the relevant tuple to see if it has
changed since it was last read.

Regards, Dave.

Responses

pgadmin-hackers by date

Next:From: Dave PageDate: 2002-02-23 21:12:33
Subject: Re: ALTER VIEW
Previous:From: Jean-Michel POUREDate: 2002-02-23 19:59:25
Subject: Schema unique stamp (OID, MD5?)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group