Re: MySQL versus Postgres

Hello

2010/8/7 Martin Gainty <mgainty@hotmail.com>:
> Ray--
>
> I would like to see in postgres:
> 1)Clustering
> 2)a more user-friendly interface to packages


> 3)eliminate the requirement to create a postgres user to execute the server
> binaries..I guess i never understood that requirement
>

it is simply - security - when pg run under root and somebody hacks
it, then he has a admin rights. When pg will run under postgres and
somebody hacks it the he have access only to database.

Regards

Pavel Stehule


> I would like to see in MySQL:
> A progression back to OpenSource ..i dont see Oracle championing 2 database
> products simultaneously
> although under the same roof it would seem the engineering resources
> currently devoted to Oracle features could easily be re-factored to MySQL..
> a prime example of a much needed requirement for MySQL ..When will MySQL
> implement row-level locking instead of just table-level locking?
>
> Martin Gainty
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> destinataire prévu, nous te demandons avec bonté que pour satisfaire
> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
> de ceci est interdite. Ce message sert à l'information seulement et n'aura
> pas n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>
>
>> Date: Sat, 7 Aug 2010 14:11:29 +0100
>> From: rod@iol.ie
>> To: masivakumar@gmail.com
>> CC: pgsql-general@postgresql.org
>> Subject: Re: [GENERAL] MySQL versus Postgres
>>
>> On 07/08/2010 11:24, சிவகுமார் மா wrote:
>> > 2010/8/7 Alban Hertroys<dalroi@solfertje.student.utwente.nl>:
>> >> On 7 Aug 2010, at 5:19, Sandeep Srinivasa wrote:
>> >>
>> >>> +1 on this.
>> >>> This is very interesting from the point-of-view of transitioning MySQL
>> >>> webapps to Postgres. The truth is that for a lot of people, MySQL is their
>> >>> first DB (because of loads of pre-existing software. Refer to my thread
>> >>> "Which CMS/Ecommerce/shopping cart"). When we are ready to move to PG, we
>> >>> are already used to the MySQL way of doing things.
>> >>
>> >
>> > As it was happening in the last 10 years, PostgreSQL will slowly
>> > gather more acceptance and MySQL will reduce in popularity down the
>> > years. But, we should help the process along.
>> >
>> > 1. Almost all webhosting providers have MySQL support, but PostgreSQL
>> > support is available from only a few who also have MySQL support.
>> > Hence MySQL is universal and PostgreSQL is present as also available.
>> >
>> > 2. Books.
>> > In a book store (where I live), technical sections have SQL, SQL
>> > Server, PHP and MySQL, Oracle racks. There is no PostgreSQL rack.
>> >
>> > 3. Name
>> > It is difficult to bring up the name in conversation.
>> >
>> > To break these circles:
>> >
>> > 1. Study a typical web hosting set up and work on supporting
>> > everything (Wordpress, Drupal, OS Commerce) with PostgreSQL.
>> > PostgreSQL only servers should be made possible.
>> >
>> > 2. Bring out more books
>> >
>> > a. Documentation is already available (PostgreSQL User Manual,
>> > PostgreSQL Technical Documentation). Re-package them and publish as
>> > books targeting different user levels.
>> >
>> > b. Cook Books can be created from the discussions in this mailing list.
>> >
>> > c. More PHP+PostgreSQL books should be created.<Professional PHP6>
>> > from Wrox uses PostgreSQL as the default db.
>>
>> Yes, so does "Pro PHP" from Apress, though it doesn't mention PG on the
>> cover. There was a nice warm glow of "goes without saying..." about it,
>> as I remember. :-)
>>
>> > 4. A pet name
>> > Is it possible to have a pet name which can be used in casual
>> > conversation easily?
>>
>> "Postgres" or "PG" are the usual, AIUI.
>>
>> Ray.
>>
>> --
>> Raymond O'Donnell :: Galway :: Ireland
>> rod@iol.ie
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>