Command Prompt Inc., a PostgreSQL consulting and support company, writes about Postgres, high availability, and open source.
Commenters name it as a large Postgres contributor with strong community mindshare, and mention its hot standby product and its PgManage tool.
> I don't see a lot of harm from adding this syntax however as people are free to not use it and it relies on an existing strict convention.
This is a good argument I will add to the list.
Also interesting to read about un-enforced foreign keys. I haven't used MSSQL myself, the DB in which I heard it's possible, I've only been using PostgreSQL for the last 20 years, and before that MySQL.
I think the problems you describe is an argument against a WITH NOCHECK feature, since it could be misused. Maybe it's necessary in some databases still, but at least in PostgreSQL, the FOR KEY SHARE lock solved all the issues with concurrent updates we had at Trustly. The FOR KEY SHARE was a huge patch [1] written mainly by Alvaro Herrera. Thanks to it, Trustly has never since had any performance problems with foreign keys, and they have AFAIK not needed to drop any foreign keys up until today due to locking/performance problems.
[1] https://www.commandprompt.com/blog/fixing_foreign_key_deadlocks_part_three/
If you want to tune your database to squeeze every single Mhz and MB on your machine then indeed you need to take the time to learn the parameters that PostgreSQL offers you, and it does offer you those parameters, it's an extra compared to MySQL. But you don't have to, you can pretty much limit yourself to a few configuration parameters that are very useful and would get you 80% of the way, and of course add some monitoring, especially for slow queries.
A good starting point for setting up a database is here: http://www.commandprompt.com/blogs/joshua_drake/2010/03/5_steps_to_postgresql_performance/
You can just throw money at Postgres problems and make them go away. There are a number of very capable firms that do nothing but Postgresql support. And, they don't hold you captive w/ licensing. And if your needs are really that unique they can help you with building extensions to postgresql that support the capabilities you need.
See http://www.commandprompt.com/support/ for an example, or http://pgexperts.com/services.html
Hi, pgmanage dev here. PgManage is being developed by CommandPrompt Inc. https://www.commandprompt.com/about/
Speaking of supply-chain attacks like the one happened with .XZ compressor - we are taking this matter seriously. I recommend to download PgManage builds from the Github releases page https://github.com/commandprompt/pgmanage/releases Cheers!
You could always hire someone like command prompt to do it for you (i'm pretty sure they already have all this stuff pre-written).
heh..actually..it's the first thing on their product list: http://www.commandprompt.com/products/hot_standby_drbd/ ... they also do clusters, etc.
for the consulting firm question http://www.enterprisedb.com/ and http://www.commandprompt.com/ are large contributors to postgres and have great mindshare in the community