Command Prompt Blog
commandprompt.com · Company blog · on HN since 2008
Command Prompt Inc., a PostgreSQL consulting and support company, writes about Postgres, high availability, and open source.
What HN saysCommenters name it as a large Postgres contributor with strong community mindshare, and mention its hot standby product and its PgManage tool.
16HN people shared it
8linked it in comments
21stories submitted
174story points
1 year agolast shared
2008people per year2026
Most-shared posts
- 1Null characters in Postgres: workarounds aren’t good enough2 people · 92 points · first shared 2020 · 47 comments on HN
- 2Homepage2 people · first shared 2009
- 3The Fall of Open Source1 people · 38 points · first shared 2016 · 21 comments on HN
- 4What MySQL (and really, Sun) can learn from PostgreSQL1 people · 7 points · first shared 2008 · 4 comments on HN
- 5Snap packages for 9.3.15, 9.4.10, 9.5.5 and 9.6.1 available1 people · 7 points · first shared 2016 · 1 comments on HN
- 6PostgreSQL High Availability options1 people · 4 points · first shared 2010 · discussion on HN
- 7PostgreSQL is King Last week was quite busy being a servant1 people · 4 points · first shared 2015 · discussion on HN
- 8GNU and the FSF should be split up1 people · 3 points · first shared 2013 · discussion on HN
- 9Postgres is better than MySQL but not because of how long it took to fix a bug1 people · 3 points · first shared 2017 · 1 comments on HN
- 10Bridging the PostgreSQL Chasm1 people · 2 points · first shared 2017 · discussion on HN
- 11PostgreSQL 7.4, 8.0 and 8.1 END OF LIFE1 people · 2 points · first shared 2010 · discussion on HN
- 12PostgreSQL v10: An Amplified version of PostgreSQL1 people · 2 points · first shared 2017 · discussion on HN
- 13PostgreSQL and Financial Calculations – Part One1 people · 2 points · first shared 2022 · discussion on HN
- 14Thoughts on Forks and Open Source Licenses1 people · 1 points · first shared 2021 · discussion on HN
- 15Is it time for a newbie-hacker mentor for PostgreSQL.Org?1 people · 1 points · first shared 2018 · discussion on HN
What HN people wrote when they linked it
jdagostino · 2010-07-26
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
eug3nix · 2024-07-22
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!
bayareaguy · 2009-05-26
Too bad you're not willing to consider PostgreSQL. I would have suggested http://www.commandprompt.com
ironchef · 2012-04-30
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.
dialtone · 2010-03-29
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_pos…
olefoo · 2009-04-24
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
lneves · 2008-04-19
Did you read the linked presentation?
http://www.commandprompt.com/files/mysql_learn.pdf
JoelJacobson · 2021-12-30
> 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_t…