Re: Upgrading a database dump/restore

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Mark Woodward" <pgsql(at)mohawksoft(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Upgrading a database dump/restore
Date: 2006-10-09 16:38:14
Message-ID: 200610090938.14679.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark,

> No one could expect that this could happen by 8.2, or the release after
> that, but as a direction for the project, the "directors" of the
> PostgreSQL project must realize that the dump/restore is becomming like
> the old locking vacuum problem. It is a *serious* issue for PostgreSQL
> adoption and arguably a real design flaw.

"directors"? (looks around) Nobody here but us chickens, boss.

If you're really interested in pg_upgrade, you're welcome to help out. Gavin
Sherry, Zdenek, and Jonah Harris are working on it (the last separately, darn
it).

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-10-09 16:43:18 Re: Upgrading a database dump/restore
Previous Message Teodor Sigaev 2006-10-09 16:32:42 Re: Backbranch releases and Win32 locking