Re: Upgrading a database dump/restore - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Upgrading a database dump/restore
Date
Msg-id 200610090938.14679.josh@agliodbs.com
Whole thread Raw
In response to Re: Upgrading a database dump/restore  ("Mark Woodward" <pgsql@mohawksoft.com>)
Responses Re: Upgrading a database dump/restore  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Upgrading a database dump/restore  ("Mark Woodward" <pgsql@mohawksoft.com>)
List 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


pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: Backbranch releases and Win32 locking
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Upgrading a database dump/restore