pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: upgrade from FC9 / PG8.3 to C7 / PG 9.6 - utf8
Date: Fri, 18 Jan 2019 17:18:45 +0200
Message-ID: <8c6bfd45-8aa5-b966-ce29-ac65b7b525b3@matrix.gatewaynet.com> (raw)
In-Reply-To: <201901181508.26233.gary.stainburn@ringways.co.uk>
References: <201901181429.51278.gary.stainburn@ringways.co.uk>
	<SN6PR11MB2976942F96E421107E5ED3E4A79C0@SN6PR11MB2976.namprd11.prod.outlook.com>
	<4e0b15ef7f84466b9370324b7f384972@imaginesoftware.com>
	<201901181508.26233.gary.stainburn@ringways.co.uk>

On 18/1/19 5:08 μ.μ., Gary Stainburn wrote:
> That is a very good question.
>
> The honest answer is because the article(s) that I have been following have
> all pointed to 9.6.  Having installed 9.6 and imported my data a couple of
> times I've found it faultless.
>
> Other than being on the latest version, what benefits and what problems would
> I encounter moving to 10.x?
>
> If I were to go to 10.x on Centos 7, would I be able to install it alongside
> the existing 9.6 to test it? I have noticed with the 9.6 install that it's
> now using the version number as part of the data path.
9.6 is not page level compatible with e.g. 9.5 whereas 10.6 is with 10.5.
So in the versioning scheme PostreSQL community just dropped one dot.
Before (<=9*) it was x.y.z with all x.y.* being compatible whereas now (>=10*) it is x.y with all x.* being compatible.
By compatible we mean that no pg_dump/restore or pg_upgrade is needed, just recompile and install.
>
> As a side question, I will be moving PHP5 on my old box to PHP7 on my new one.
> Is there any gotcha's I need to worry about?
>
> On Friday 18 January 2019 14:52:25 David Modica wrote:
>> sorry, slightly off point but I am a newbie and I was wondering gary,
>>
>> why aren't you going to  postgresql 10.X  ? I keep thinking
>>
>> that I should stay as current as possible. should I relax about that ?
>>
>> david
>>
>> From: Scott Whitney <scott@journyx.com>
>> Sent: Friday, January 18, 2019 9:31 AM
>> To: Gary Stainburn <gary.stainburn@ringways.co.uk>; pgsql-admin
>> <pgsql-admin@postgresql.org> Subject: Re: upgrade from FC9 / PG8.3 to C7 /
>> PG 9.6 - utf8
>>
>>
>> So long as you use pg_dump from PG 9 to dump the PG 8 databases, you'll be
>> fine.
>>
>>
>>
>> en_GB.UTF-8 will be fine (and is probably preferred).
>>
>> ________________________________
>> From: Gary Stainburn <gary.stainburn@ringways.co.uk>
>> Sent: Friday, January 18, 2019 8:29 AM
>> To: pgsql-admin
>> Subject: upgrade from FC9 / PG8.3 to C7 / PG 9.6 - utf8
>>
>> I'm performing a long overdue upgrade of a Fedora 9 / Postgresql 8.3 to a
>> Centos 7 / Postgresql 9.6 system.
>>
>> I'm just going though the config files to check that everything is okay and
>> I've found a discrepency regarding language settings.  I realise things
>> have progressed a lot since 2008 when I built this server, so I wonder what
>> is the right thing to do moving forward.  The old system has
>>
>> # These settings are initialized by initdb, but they can be changed.
>> lc_messages = 'en_GB'   # locale for system error message  strings
>> lc_monetary = 'en_GB'   # locale for monetary formatting
>> lc_numeric = 'en_GB'    # locale for number formatting
>> lc_time = 'en_GB'               # locale for time formatting
>>
>> while the new system has
>>
>> lc_messages = 'en_GB.UTF-8'     # locale for system error message strings
>> lc_monetary = 'en_GB.UTF-8'     # locale for monetary formatting
>> lc_numeric = 'en_GB.UTF-8'      # locale for number formatting
>> lc_time = 'en_GB.UTF-8'         # locale for time formatting
>>
>> Am I best changing the new system to match the old one?
>> If I leave the settings as they are, enabling the utf-8, how will it affect
>>          a) the pg_dumpall / pg_recover process
>>          b) using the database moving forward?
>>
>> Gary
>>
>>
>> [Image removed by sender.]
>>
>> [Image removed by sender.]<https://www.linkedin.com/company/journyx-inc/;
>> [Image removed by sender.] <https://www.twitter.com/journyxinc;
>>
>> [Image removed by sender.]
>>
>>
>> Scott Whitney
>> Director of IT
>>
>> [Image removed by sender.]
>>
>> scott@journyx.com<mailto:scott@journyx.com> | +1 (800) 755-9878
>>
>> 7600 Burnet Road, Ste. 300
>> Austin, TX 78757
>>
>> Visit us at www.journyx.com<https://www.journyx.com/;
>>
>>
>> To unsubscribe from Journyx promotional emails, click here
>> <http://journyx.com/communication-preferences; or visit
>> http://journyx.com/communication-preferences.
>
>


-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt





view thread (11+ messages)  latest in thread

Message-ID: <8c6bfd45-8aa5-b966-ce29-ac65b7b525b3@matrix.gatewaynet.com>
Permalink:  ../8c6bfd45-8aa5-b966-ce29-ac65b7b525b3@matrix.gatewaynet.com/
Also on:    postgresql.org/message-id/8c6bfd45-8aa5-b966-ce29-ac65b7b525b3@matrix.gatewaynet.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: achill@matrix.gatewaynet.com
  Subject: Re: upgrade from FC9 / PG8.3 to C7 / PG 9.6 - utf8
  In-Reply-To: <8c6bfd45-8aa5-b966-ce29-ac65b7b525b3@matrix.gatewaynet.com>
  References: <201901181429.51278.gary.stainburn@ringways.co.uk> <SN6PR11MB2976942F96E421107E5ED3E4A79C0@SN6PR11MB2976.namprd11.prod.outlook.com> <4e0b15ef7f84466b9370324b7f384972@imaginesoftware.com> <201901181508.26233.gary.stainburn@ringways.co.uk> <8c6bfd45-8aa5-b966-ce29-ac65b7b525b3@matrix.gatewaynet.com>

* 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