From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] postgresql updates
Date: Thu, 10 Feb 2011 18:18:28 +0100 [thread overview]
Message-ID: <ij16l4$3d9$1@dough.gmane.org> (raw)
In-Reply-To: <4D541B37.6050404@mentor.com>
-----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-----
prev parent reply other threads:[~2011-02-10 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 16:17 [RFC] postgresql updates Tom Rini
2011-02-10 16:44 ` Koen Kooi
2011-02-10 17:07 ` Tom Rini
2011-02-10 17:18 ` Koen Kooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ij16l4$3d9$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.