[Spacewalk-list] Recommended Database backend for 1.7

[Paul Robert Marino]

Oracle is the old standard safe route.
PostgreSQL is where the development is going.
Not all of the functions are ported to PostgreSQL yet but its getting
closer with every release.
That being said there have been incidents on the list of some Oracle
compatibility issues popping up however they can mostly be worked
around by taking greater care while setting up Oracle. For example one
that pops into my mind is the default Character encoding in the
database should be set to UTF-8 which is not the default for many
Oracle versions.

In other words as of 1.7 Oracle is still the safer route for now,
however this will probably change in future versions.




On Mon, Apr 23, 2012 at 12:42 PM, Trent Johnson <tljohnsn at oreilly.com> wrote:
> Hi Folks,
>
> I am doing the same thing.  I've searched the list and this has been asked a
> few times with no replies.  I'd like to deploy 1.7 with postgres on centos 6
> for production if possible.
>
> Also - thanks to everyone working on spacewalk - I haven't upgraded since
> 1.3, but did update all the way to 1.7 today and it all went fine.  Lot's of
> improvements.
>
> Thanks,
> Trent
>
> sent from a mobile device
>
> On 03/08/2012 02:57 PM, Coy Hile wrote:
>>
>> Hi all,
>>
>> Is there a recommended back end for Spacewalk 1.7 (installing on RHEL
>> 6)?  From what I saw in the descriptions of the 1.7 release, it looks
>> like there's now feature parity between Oracle and PostgreSQL as far as
>> Spacewalk features are concerned.
>>
>> Thanks,
>> -Coy
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list