> It's more like a question of best practice: > How do you managing different version of database layout for e.g. > software releases? > We are planing to do an application based on postgres and want to store > some version number of database layout to ensure correct upgrade-scripts > can be applied in case of an upgrade. Is there any build in for? We (www.gnumed.de) generate the md5 of a concatenation of the database layout (tables/columns/PKs) which the client checks against and disconnects if there's a mismatch. Karsten -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general