Thread: [GENERAL] Any known issues Pg 9.3 on Ubuntu Xenial kernel 4.4.0?
Basically as per $subject. We took a perf hit moving up to newer hardware and OS version which might in some cases be OK but admittedly there is some risk running a much older app (Pg 9.3) on a kernel/OS version that nowhere near existed when 9.3 was current. Be curious to hear of issues encountered and particular to eager to know if disabling any kernel 4.x features helped. Thanks PostgreSQL 9.3.19 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit $ uname -a Linux foo.somehost.com 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On Wed, Sep 20, 2017 at 01:14:14PM -0500, Jerry Sievers wrote: > Be curious to hear of issues encountered and particular to eager to know > if disabling any kernel 4.x features helped. What was the old kernel/OS ? wheezy / kernel 3.x ? Perhaps try these ideas ? https://www.postgresql.org/message-id/20170718180152.GE17566%40telsasoft.com Justin -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On Wed, Sep 20, 2017 at 12:14 PM, Jerry Sievers <gsievers19@comcast.net> wrote: > Basically as per $subject. > > We took a perf hit moving up to newer hardware and OS version which > might in some cases be OK but admittedly there is some risk running a > much older app (Pg 9.3) on a kernel/OS version that nowhere near existed > when 9.3 was current. Are you sure you're using the same locale etc as you were on the old db? The most common cause of performance loss when migrating is that the new db uses a locale like en_US while the old one might have been in locale=C > > Be curious to hear of issues encountered and particular to eager to know > if disabling any kernel 4.x features helped. > > Thanks > > PostgreSQL 9.3.19 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit > > > $ uname -a > Linux foo.somehost.com 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > > -- > Jerry Sievers > Postgres DBA/Development Consulting > e: postgres.consulting@comcast.net > p: 312.241.7800 > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general -- To understand recursion, one must first understand recursion. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Scott Marlowe <scott.marlowe@gmail.com> writes: > On Wed, Sep 20, 2017 at 12:14 PM, Jerry Sievers <gsievers19@comcast.net> wrote: > >> Basically as per $subject. >> >> We took a perf hit moving up to newer hardware and OS version which >> might in some cases be OK but admittedly there is some risk running a >> much older app (Pg 9.3) on a kernel/OS version that nowhere near existed >> when 9.3 was current. > > Are you sure you're using the same locale etc as you were on the old > db? The most common cause of performance loss when migrating is that > the new db uses a locale like en_US while the old one might have been > in locale=C No change there. enUS-utf8 in both cases. Thanks > >> >> Be curious to hear of issues encountered and particular to eager to know >> if disabling any kernel 4.x features helped. >> >> Thanks >> >> PostgreSQL 9.3.19 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit >> >> >> $ uname -a >> Linux foo.somehost.com 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux >> >> -- >> Jerry Sievers >> Postgres DBA/Development Consulting >> e: postgres.consulting@comcast.net >> p: 312.241.7800 >> >> >> -- >> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-general > > > > -- > To understand recursion, one must first understand recursion. -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general