From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org, jm(dot)poure(at)freesurf(dot)fr, Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Subject: | Re: Schema unique stamp (OID, MD5?) |
Date: | 2002-02-24 08:52:20 |
Message-ID: | twXWGtZbz5b3.CZKyH3D3@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Sorry, I don't understand what you are asking.
/D
_____________Original message ____________
Subject: Re: [pgadmin-hackers] Schema unique stamp (OID, MD5?)
Sender: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
Date: Sun, 24 Feb 2002 08:49:07 +0000
Le Samedi 23 Février 2002 21:53, Dave Page a écrit :
> 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.
What if you create a trigger on a function which does not exist anymore. Is
there a way to query a unique OID?
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-02-24 15:04:45 | Escaping quotes and double-quotes problem |
Previous Message | Jean-Michel POURE | 2002-02-24 08:46:59 | Working oin pgAdmin2 |