| From: | Chris Browne <cbbrowne(at)acm(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [pgsql-www] commitfest.postgresql.org |
| Date: | 2009-07-08 16:59:46 |
| Message-ID: | 877hyj156l.fsf@dba2.int.libertyrms.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
robertmhaas(at)gmail(dot)com (Robert Haas) writes:
> I suspect both are true, but in the unlikely event that we decide on
> some massive change to the system, we can either run the DBs in
> parallel as Tom suggests, or dump out the older data in Wiki markup
> and post it on there. But I can't imagine what we'd want to do that
> would even make us consider such drastic steps. Your example would
> not be a difficult migration, for instance.
We had an ancient version of Bugzilla in use for quite a while; it was
*SO* vastly different from modern versions that it wasn't remotely
plausible to port the data from the old instance to a new one.
I went and ran "wget" to pull all the contents of the old instance,
turning that into a series of static web pages. No longer updatable,
but certainly browsable.
Once a CommitFest is complete, I could easily see making a summary of
it, as a series of static web pages. No need for a database anymore
altogether ;-).
--
select 'cbbrowne' || '@' || 'linuxfinances.info';
http://linuxdatabases.info/info/spreadsheets.html
I'd give my right arm to be ambidextrous!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-08 17:31:19 | Re: 8.4.0 vs. locales vs. pl/perl? |
| Previous Message | Andrew Dunstan | 2009-07-08 16:57:43 | Re: multi-threaded pgbench |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-07-08 18:25:44 | Re: [HACKERS] commitfest.postgresql.org |
| Previous Message | Dave Page | 2009-07-08 07:57:34 | Re: Sourceforge PG release |