| Lists: | pgsql-hackers |
|---|
| From: | "Serguei A(dot) Mokhov" <mokhov(at)cs(dot)concordia(dot)ca> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Resurrecting pg_upgrade |
| Date: | 2004-08-31 20:13:38 |
| Message-ID: | Pine.LNX.4.58.0408311540420.21361@haida.cs.concordia.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Hello,
Just poking around to see if anyone is working on resurrecting the concept
of pg_upgrade after all these years? If not, I think I have nearly ready a
high-level design of how the whole upgrade procedure will work, but I just
need to clear out some ideas and put them together in a more-or-less
coherent way. If nobody's working on the feature, I'd like to tackle it
for 8.1/8.2 after having the design approved by the community.
To clarify some of these, I would like to identify the codepaths, more
generally -- directories with the code that, if changed, forces initdb.
I'd assume these would fall into this category:
src/backend
/storage
/smgr
*
/access
/bootstrap
/catalog
/commands
If you have time, please make the list above more complete or remove
extraneous items.
Please Cc to me as I am on the digest on most pg lists.
Thank you,
--
Serguei A. Mokhov | /~\ The ASCII
Computer Science Department | \ / Ribbon Campaign
Concordia University | X Against HTML
Montreal, Quebec, Canada | / \ Email!
| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | "Serguei A(dot) Mokhov" <mokhov(at)cs(dot)concordia(dot)ca> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Resurrecting pg_upgrade |
| Date: | 2004-09-01 08:45:56 |
| Message-ID: | 41358C44.9010405@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Serguei A. Mokhov wrote:
> Hello,
>
> Just poking around to see if anyone is working on resurrecting the concept
> of pg_upgrade after all these years?
You probably want to join the (very recent) thread subject = "version
upgrade" started by Andrew Rawnsley.
--
Richard Huxton
Archonet Ltd
| From: | "Serguei A(dot) Mokhov" <mokhov(at)cs(dot)concordia(dot)ca> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Resurrecting pg_upgrade |
| Date: | 2004-09-01 17:42:15 |
| Message-ID: | Pine.LNX.4.58.0409011338360.15314@respect.services.encs.concordia.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On Wed, 1 Sep 2004, Richard Huxton wrote:
> Date: Wed, 01 Sep 2004 09:45:56 +0100
>
> Serguei A. Mokhov wrote:
> > Hello,
> >
> > Just poking around to see if anyone is working on resurrecting the concept
> > of pg_upgrade after all these years?
>
> You probably want to join the (very recent) thread subject = "version
> upgrade" started by Andrew Rawnsley.
Being on the digest mode I just came across it. Reading it doesn't give
much more concrete stuff yet. I think I will finalize my design and post
it then, but the reply to my original post with initdb-forcing code paths
would be helpful anyway to all.
Thanks for the reply though!
--
Serguei A. Mokhov | /~\ The ASCII
Computer Science Department | \ / Ribbon Campaign
Concordia University | X Against HTML
Montreal, Quebec, Canada | / \ Email!