Hi.

I have googled and googled for good, simple instructions to upgrade
from 8.2.3 to 8.3.3 (latest stable at this time?)

I am on a Cpanel interface. Use Apache and PHP for most of my websites.

This seems to be the most often quoted resource on forums etc:

http://kb.linuxnetworkcare.com/node/21

But this suggests backing up, then UNinstalling (downtime and loss of
settings!), then REinstalling postgresql.

Is there no sensible way of simply upgrading the database engine
without affecting either the uptime or the data itself?

I really really do not wish to backup gigabytes worth of data and then
reupload it back into the DB. This represents a downtime of *at least*
an hour or so, which our busy website doesn't have.

Any thoughts or pointers?

Thanks!

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

> > If you're going to run slony, then the pg_dump|pg_restore step is
> > completely wasted. Slony will restore all the data again. You do
> > need to run pg_dump -s, of course.




Thanks to everyone who replied. We have no experience with this
"Slony". Any simple instructions on installing it and getting it
working?

Why is PG so complex! It's a such a lovely database. If only at least
the installation and upgrade could be made more humane..

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Tue, 26 Aug 2008 09:25:09 +0800
"Phoenix Kiula" <phoenix.kiula@gmail.com> wrote:

> "Slony". Any simple instructions on installing it and getting it
> working?
>
> Why is PG so complex! It's a such a lovely database. If only at least
> the installation and upgrade could be made more humane..
>

Well the installation is about as easy as it gets. I grant you we are
in the stone age when it comes to upgrading. We are however welcoming
patches should you feel the need to create and or sponsor

Joshua D. Drake

--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate



--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Mon, Aug 25, 2008 at 7:25 PM, Phoenix Kiula <phoenix.kiula@gmail.com> wrote:
>> > If you're going to run slony, then the pg_dump|pg_restore step is
>> > completely wasted. Slony will restore all the data again. You do
>> > need to run pg_dump -s, of course.
>
>
>
>
> Thanks to everyone who replied. We have no experience with this
> "Slony". Any simple instructions on installing it and getting it
> working?
>
> Why is PG so complex! It's a such a lovely database. If only at least
> the installation and upgrade could be made more humane..

Any database that has real ACID guarantees is going to be complex.
Some more than others. I think that upgrading postgresql in place is
a LOT of work and not the highest priority, and slony lets you upgrade
LIVE. Note that you cannot upgrade an Oracle installation from 9g to
10i live. You take it offline from the app, migrate your data, and
start up the new database.

Slony replication lets postgresql accomplish this, which is really
quite impressive. We just upgraded from an 8.1 server to an 8.3
server via slony, and it went smooth as silk. db downtime was
measured in seconds.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On 8/26/08, Phoenix Kiula <phoenix.kiula@gmail.com> wrote:
> On 8/26/08, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> >
> > Slony replication lets postgresql accomplish this, which is really
> > quite impressive. We just upgraded from an 8.1 server to an 8.3
> > server via slony, and it went smooth as silk. db downtime was
> > measured in seconds.
>
>
>
>
> Thanks for this Scott. Sounds promising. But where can I find the
> instructions to install Slony, then install new PG 8.3.3, then start
> it with similar CONF settings and stuff, then setup the master and
> slave (which I am not familiar with), and then switch master and slave
> when everything is working?
>
> To others who keep telling us that "PG is complex and if you want it
> to be less so then contribute" -- well, sorry I am not that technical.
> If the intended target audience of PG is only super-techsavvy folk who
> can write C++ patches for every little functionality they need, then
> perhaps I chose the wrong DB? I doubt it.
>
> It would be really nice if the PG official community can have some
> simple instructions to make a seamless upgrade, if no simpler patches
> exist. At the very least the instructions will help us plentiful folk
> who do NOT use PG in the exalted "enterprise" setting, but to run busy
> websites. This is how MySQL became big too, by being convenient and
> reliable (until recently anyway), but I see no point in that
> discussion.
>
> Anyhow, it would be really nice to have simple instructions. Searching
> on Google for words like "Slony Postgresql upgrade" or "install slony
> with postgresql 8.3" returns stuff that makes a lot of presumptions!
>
> I have a CentOS 4 with Cpanel/WHM running. PG is in the usual place:
>
> > whereis pgsql
> pgsql: /usr/lib/pgsql /usr/include/pgsql /usr/share/pgsq
>
> Now how can I install Slony so that it install PGSQL and allows me to
> continue working with Apache/PHP for my website? I am reading this --
> http://slony.info/documentation/installation.html -- but while it
> textually mentions the stuff in the writeup, I don't see full
> instructions to install Slony, then new PGSQL, then switching, and so
> on.
>
> So many thanks for any help anyone can provide! Or point me to some
> resource that exists but is hiding from Google.
>



See, this is where I get confused. I want to upgrade from 8.2.3 to
8.3.3. The recommendation is to try Slony. So I download Slony and try
to configure it. The configure command gives me this:


----
checking for correct version of PostgreSQL... "error"
configure: error: Your version of PostgreSQL (8.2) is lower
than the required 8.3. Slony-I needs functionality included in
a newer version.
----


Well, if Slony needs a newer version, then how can it be used to upgrade?!

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On 2008-08-26 13:39, Phoenix Kiula wrote:

> Ok done. Slony is installed. Now what?

http://www.slony.info/documentation/versionupgrade.html
I think nobody would guide you step by step. Either read documentation
and do it yourself or hire an expert:
http://www.postgresql.org/support/professional_support

> I was also told that the postgresql.conf settings across 8.2 and 8.3
> are different so I cannot (or should not) use the same old
> postgresql.conf for the new database install.

Find out what changes were made to your old postgresql.conf (compare it
to the default) and make the same changes to new posgresql.conf.

Regards
Tometzky
--
....although Eating Honey was a very good thing to do, there was a
moment just before you began to eat it which was better than when you
were...
Winnie the Pooh

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On 8/26/08, Tomasz Ostrowski <tometzky@batory.org.pl> wrote:
>
> I think nobody would guide you step by step. Either read documentation
> and do it yourself or hire an expert:


Thanks. I suppose that spirit is quite evident in the documentation.
Why make it easy or easily understandable when you can win fanatical
fans by requiring them to invest months of their time!

Cheers.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Tue, Aug 26, 2008 at 5:02 AM, Tomasz Ostrowski
<tometzky@batory.org.pl> wrote:

> http://www.slony.info/documentation/versionupgrade.html
> I think nobody would guide you step by step.

Well they may, then is nothing wrong with asking especially when
"breaking new ground." Since my databases are currently pretty small,
a dump and reload is not a problem. However, I am following this
tread with keen interest for future reference. Perhaps others are
also?

> Either read documentation
> and do it yourself or hire an expert:
> http://www.postgresql.org/support/professional_support

Reading the documentation is always good advice. Ofcourse, I think
that DBA/SA wants and should be able to perform all tasks associated
with maintaining a database. However, I very much agree that buying a
support aggreement for "mission critical" applications is an important
safety net to have.


> Find out what changes were made to your old postgresql.conf (compare it
> to the default) and make the same changes to new posgresql.conf.

I very much agree. There wasn't that much that changed between 8.2
and 8.3. Just look for the uncommented postgresql.conf setting in 8.2
and then compare with 8.3.


--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Mon, Aug 25, 2008 at 08:36:34PM -0600, Scott Marlowe wrote:

> Slony replication lets postgresql accomplish this, which is really
> quite impressive.

Pleased as I am to hear accounts of Slony being used successfully to
solve the upgrade problem -- it was one of our design goals in the
early discussions at Afilias -- I have to confess that if you find
Postgres administration arcane, Slony administration is going to seem
very like interpreting runes.

I have heard that Londiste (in the skytools package) can also do this,
and it is intended to be easier to administer. I have no personal
experience trying it.

A

--
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Tue, Aug 26, 2008 at 5:31 AM, Phoenix Kiula <phoenix.kiula@gmail.com> wrote:

> I suppose that spirit is quite evident in the documentation.
All kidding aside, the problem that you are having IS recognized as a
weakness with PostgreSQL. This is why some are already working on
solving the problem of in place upgrades. Some time in the future
perhaps > 8.4 this will be a mute point. In the meantime, there are
other workarounds (which of course can be complex) to mitigate this
problem.

> Why make it easy or easily understandable when you can win fanatical
> fans by requiring them to invest months of their time!

I sense your frustration. But it is important to remember that the
PostgreSQL project is largely supported by volunteers. I am sure that
you agree that no one intentionally designs any give task to be more
complicated than necessary. As a side note there are many useful "how
to" articles on the web. Many of these HOWTOs were created by users
(like yourself) that have faced a difficult problem with no apparent
solution. However, after struggling with the problem and then finding
a solution, they document it for all to benefit from. Perhaps some
good with come from overcoming this challenge.

So in the mean time, the best advice is not to rush time upgrade but
take your time to insure that you do it right the first time.
Some useful article that you should consider are:
http://www.depesz.com/index.php/2008...how-to-fix-it/
http://people.planetpostgresql.org/g...s-learned.html




--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general