On 06/09/2017 11:58 AM, Tobias May wrote:
> Mellow Greetings all,
>
> I'm a junior DBA and PostgreSQL-enthusiast. Last year I switched to a
> company where they promised to me the opportunity to dive deeper into
> PostgreSQL.
>
> At that time there was a lead developer, who was a
> PostgreSQL-enthusiast, too. And there was an agreement that PostgreSQL
> is the primary database backend for our product. Unfortunately she has
> been frozen out by non-technical decision makers. Now there is only one
> colleague and me (without authority to decide) left to advocate PostgreSQL.
>
> Most of the developers in the company are used to MySQL. Although they
> seem to accept PostgreSQL some still subtly question the decision and
> I'm feeling, that I have to constantly defend the decision for PostgreSQL.
In general people resist change especially when they out-number you. It
usually does not come to better or worse but what I know versus the
unknown. If you do not have the power to force the change then you are
left with leading by example. Create test cases that demonstrate the
features of Postgres and how it makes you more productive. Ask what it
is that the developers like about MySQL and show the analogue in
Postgres. Ask what they don't like about Postgres and see if the
argument is valid or can be refuted.
>
> To me all these political and technical advantages of PostgreSQl over
> MySQL are more than enough. But the results don't feel "resilient"
> enough. It is also cumbersome to keep track of how far ahead PostgreSQL
> is in comparison of features and standards compliance and providing
> undeniable practical examples.
>
> Finally:
> How do I convince people to choose PostgreSQL over a MySQL?
> Alternatively:
> How do I cope with people, which refuse the available (too few?) facts?
Ask them to join the pgsql-general list and see the community at work.
Point them at:
https://www.postgresql.org/about/events/
>
> Thank you so much for this little gem called PostgreSQL. Keep up the
> great work.
>
>
> Be well,
>
> Tobias
>
--
Adrian Klaver
adrian.klaver@aklaver.com
