A long time ago, in 2010, I've had the same type of meeting at the company that
I was working for at the time.
https://www.meetup.com/postgresql-3/messages/boards/thread/9965998
The meeting ended like this:
There was a huge row on the Postgres mailing lists about hints. Hints have
since become a part of Postgres. A pastry baker from Portlaand
wrote an article that only someone like him could write:
http://it.toolbox.com/blogs/database-soup/why-postgresql-doesnt-have-query-hints-44121?rss=1
I still use that article to illustrate everything that's wrong with Postgres.
Postgres official "todo" list still contains a paragraph about the
non-wanted hints (https://wiki.postgresql.org/wiki/Todo). Of course, there
are also the following sites:
- http://pghintplan.osdn.jp/pg_hint_plan.html
- https://github.com/ossc-db/pg_hint_plan
- https://osdn.net/projects/pghintplan/
So, the official stance toward hints is that hints are bad and "we don't want
them". Hints are there, available for the most of the major versions in use
today. Furthermore, partitioning is still a joke. No global indexes, optimizer
still unable to correctly calculate plan for the partitioned tables.
Parallelism is implemented in PgSQL 9.6, parallel query is available. However,
partitioning and the developer community attitudes are still a problem. I would
be vewy, vewy caweful with transitioning from Oracle to an open source DB. My
primary candidate for such a transition would still be MariaDB, which has
in-memory option and can optionally use Cassandra as the storage engine. I am
no longer a DBA, but I would still advise against transitioning to PostgreSQL.
It's still not good enough, when compared to the other open source databases
and the developer community is still hostile toward the user feature requests.
If something that you need is missing from PgSQL, the chances of getting
it are slim at best. As a matter of fact, the attitude expressed by my
favorite pastry baker is still the pervasive attitude in the PostgreSQL
community. As long as that is the case, Postgres is simply too big of a risk to
transition to.
Regards
On Tue, 11 Jul 2017 10:22:28 -0700
"Joshua D. Drake" <jd@xxxxxxxxxxxxxxxxx> wrote:
Folks,
There have been some members who have expressed interest in $SUBJECT. As
an FYI, there is an Oracle to Postgres training happening at:
Postgres Conference Seattle
https://pgconf.us/conferences/Seattle2017
Thanks,
JD
