Big Test Environment Feature

From: Matthew Tedder <matthew(at)tedder(dot)com>
To: hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Big Test Environment Feature
Date: 2002-06-14 15:12:33
Message-ID: 20020614180709.58C954762B1@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Question:

How feasible would it be to create this functionality in PostgreSQL:

One creates a test version of a database that initially consists of
read-links to the production version of the same database. Any code he/she
then writes that reads from a table reads from the production database but
any code that modifies data copies that table to the test database.

The benefits of this are obviously huge for IT shops that need to constantly
work on data in test environments as similar as possible to the production
environment.

Usually, this is a very difficult aspect of one's work and represents a great
deal of risk. We always try to hard to ensure that what we migrate into
production is going to work there the same as it did in test. And we should
not do testing in a production environment.

Such a feature would give PostgreSQL a major advantage over Oracle or DB2.

And some day when PostgreSQL is also distributable, it'll be ideal for the
enterprise.

Matthew

--
Anything that can be logically explained, can be programmed.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2002-06-14 16:10:45 Re: SQL99 feature list
Previous Message Thomas Lockhart 2002-06-14 14:59:01 SQL99 feature list