pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Silvio Brandani <silvio.brandani@tech.sdb.it>
To: Gabriele Bartolini <Gabriele.Bartolini@2ndQuadrant.it>
Cc: Iñigo Martinez Lasala <imartinez@vectorsf.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: upgrade postgres 8.1.21 to version 8.3.6
Date: Wed, 14 Jul 2010 16:44:51 +0200
Message-ID: <4C3DCD63.5040706@tech.sdb.it> (raw)
In-Reply-To: <c3e15c443c8ea72f2a036f047b2d3161@mail.xcon.it>
References: <4C3C322C.4050305@tech.sdb.it>
	<1279054371.13317.130.camel@deimos>
	<c3e15c443c8ea72f2a036f047b2d3161@mail.xcon.it>

Gabriele Bartolini ha scritto:
> Ciao Silvio,
>
> On Tue, 13 Jul 2010 22:52:51 +0200, Iñigo Martinez Lasala
>   
>> You should script database migration process in order to make it faster.
>> Upgrading binaries is really simple. A yum upgrade should be enough.
>>     
>
> Yes, faster and repeatable. Something you can launch with a script that
> does everything from scratch. As Iñigo was pointing out, you must pay a lot
> of attention in setting up a test environment which helps you:
>
> * simulate the migration process (and gives you accurate measures of
> times)
> * test the applications
>
> As Iñigo said, on a typical usage pattern, the most likely set of errors
> you will encounter are data type checks which require casting. Therefore it
> becomes crucial to:
>
> * setup the test database (preferably on a different server)
> * setup test applications that interface with the new Postgres database
>
> I assume you are using 8.3 because of RPM availability, isn't it?
> Otherwise, you should think of 8.4.
>
> Ciao,
> Gabriele
>
>   

I have simulate the upgrade process in a test environment -
The casting problem in effect occurs, we will provide the required 
modification at application code before proceeding with the upgrade.
thanks a lot -
Regards,


--

---






Utilizziamo i dati personali che la riguardano esclusivamente per nostre finalità amministrative e contabili, anche quando li comunichiamo a terzi. Informazioni dettagliate, anche in ordine al Suo diritto di accesso e agli altri Suoi diritti, sono riportate alla pagina http://www.savinodelbene.com/news/privacy.html
Se avete ricevuto questo messaggio per errore Vi preghiamo di ritornarlo al mittente eliminandolo assieme agli eventuali allegati, ai sensi art. 616 codice penale http://www.savinodelbene.com/codice_penale_616.html
L'Azienda non si assume alcuna responsabilità giuridica qualora pervengano da questo indirizzo messaggi estranei all'attività lavorativa o contrari a norme.
--



view thread (6+ messages)

Message-ID: <4C3DCD63.5040706@tech.sdb.it>
Permalink:  ../4C3DCD63.5040706@tech.sdb.it/
Also on:    postgresql.org/message-id/4C3DCD63.5040706@tech.sdb.it

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: silvio.brandani@tech.sdb.it, Gabriele.Bartolini@2ndQuadrant.it, imartinez@vectorsf.com
  Subject: Re: upgrade postgres 8.1.21 to version 8.3.6
  In-Reply-To: <4C3DCD63.5040706@tech.sdb.it>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox