From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lo.gmane.org ([80.91.229.12]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1PnaBF-0001Gg-QS for openembedded-devel@lists.openembedded.org; Thu, 10 Feb 2011 18:19:45 +0100 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PnaAD-0006KR-KR for openembedded-devel@lists.openembedded.org; Thu, 10 Feb 2011 18:18:41 +0100 Received: from ip545070eb.adsl-surfen.hetnet.nl ([84.80.112.235]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Feb 2011 18:18:41 +0100 Received: from k.kooi by ip545070eb.adsl-surfen.hetnet.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Feb 2011 18:18:41 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@lists.openembedded.org From: Koen Kooi Date: Thu, 10 Feb 2011 18:18:28 +0100 Message-ID: References: <4D540F81.3030205@mentor.com> <4D541B37.6050404@mentor.com> Mime-Version: 1.0 X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ip545070eb.adsl-surfen.hetnet.nl User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.16) Gecko/20101127 Shredder/3.0.11pre In-Reply-To: <4D541B37.6050404@mentor.com> X-Enigmail-Version: 1.0.1 Subject: Re: [RFC] postgresql updates X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2011 17:19:45 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10-02-11 18:07, Tom Rini wrote: > On 02/10/2011 09:44 AM, Koen Kooi wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 10-02-11 17:17, Tom Rini wrote: >>> Hey all, >>> >>> I'll post patches later but I'd like to do some upgrading / fixing to >>> postgresql. >>> >>> First, from >>> http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy >>> postgresql 8.1.x (our default) is EOL. 8.2.x will EOL this year and >>> 8.4.x has some good life left to it. >>> >>> Second, after reading the various release notes (starting on >>> http://www.postgresql.org/docs/8.2/static/release-8-2-20.html), I would >>> like to: >>> >>> - Drop 8.1.x >>> - Drop 8.2.x (since it's D_P = -1 and unpinned) >>> - Make 8.4.7 the default which means >>> - Un-pin SHR (8.4.4 to 8.4.7 is a safe and no changes needed upgrade, >>> see http://www.postgresql.org/docs/8.4/static/release-8-4-7.html) >> >> Sounds good to me! >> >>> What got me going here is that 8.1.x and 8.2.x both use ld directly for >>> linking rather than CCLD which causes problems on mips64 which means >>> qt4*demo-image was failing (well, outside of SHR ;)). >>> >>> But the question is, do we want to in any way try and prompt the user to >>> get them to upgrade their 8.1.x DB? Or just assume anyone using >>> postgresql will be smart enough to figure out they need to dump and >>> restore (if I read things right). >> >> We could at least dump something to stdout in the postinst like mysql >> does. > > I see where mysql will attempt to setup the db. Maybe mysql_install_db > (a command from mysql) does that? I installed mysql5 last week and there was a huge text about deleting test users and stuff, I haven't looked what is doing that. I assumed it was just a echo in the postinst, but it might be the actual mysql programs doign it :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNVB3kMkyGM64RGpERAm3JAJ0QvogVlUpfIUAUBDU7aWZzlWpDzACdGaPa HkA5xHjheuPol6v68ubHoOg= =cq8C -----END PGP SIGNATURE-----