It's missing the part at the end that says "for general use"
Plenty of noSQL and even MySQL/mariaDB features beat psql in the right problem space.
PostgreSQL is the worlds’ best database
21–30 of 365 posts
Re: PostgreSQL is the worlds’ best database
#22Earlier quoted context omitted.
Well, (unfortunately) plenty of applications support only one DB backend. For FOSS software, MySQL/MariaDB support is very common, and even if those apps support pgSQL it might be that pgSQL support is not as robust and well-tested as mysql. And in plenty of situations, sqlite is perfectly adequate, and saves you from the extra work of managing yet another service. But yes, I agree if I'd start from a blank sheet and…
Yahoo uses PostgreSQL. I think that's pretty high-end requirements an debunks the myth of "commercial software is better for high end requirements".
First of all, Yahoo historically used Oracle Enterprise and MySQL for RDBMS, roughly 50% each.
Large companies use some of everything, but I never saw PG in use there.
Re: PostgreSQL is the worlds’ best database
#23Earlier quoted context omitted.
MSSSQL people seem really proud of their CTEs. What is it that makes CTEs in MSSQL so great? I wonder if that really disqualifies Postgres from the same task. Are MSSQL CTEs just the hammer for your proverbial nail? Can you use a different approach in Postgres to solve the problem by leveraging its strengths? My day job is a lot of Redshift. We use CTEs and temp tables depending on what we need. It’s based on Postgre…
Here's the last line of my post: "Not that I'm knocking PG, 'best' depends upon the problem" I did not want to get into a war with people emotionally involved in their favourite programming tool. The article said 'best'. By that measure PG was worse. Point is it doesn't matter, it's about what problem you are trying to solve and at what price. In many cases PG is best for that - do you understand? I knew people would…
You do realize you are the one getting emotional because you are clinging to an engine that consistently underperforms in benchmarks across the board and costs you a fortune right?
Hope the job security is worth being an expert in a bunch of defunkt practices in 10 years nobody will want.
Re: PostgreSQL is the worlds’ best database
#24This is advertising of course. But if I had to select an SQL DB postgres is my only choice. Perhaps I don't know enough about databases and their differences. Anyone have some pros and cons of others? Like why would I pick MySQL, Microsoft, Oracle, Maria etc over Postgres? Apart from support that you gotta pay for.
Replication, failover and high availability are complicated matters. I believe there are other SQL databases that may be said to handle this better than PostgreSQL. At the very least, CockroachDB is much simpler to set up and manage. Cannot vouch for its stability and complexity of abnormal emergency recoveries, though - haven't used it long enough, only had simplest outages (that it had handled flawlessly).
>Replication, failover and high availability are complicated matters.
I wonder why Postgre hasn't improved in these areas and instead leaving it to third party solution. I mean every year these few points are still listed as something that flavours MySQL.
Re: PostgreSQL is the worlds’ best database
#25PostgreSQL is great if you:
a) are OK with using SQL (this is not obvious)
b) do not need a distributed database
I've spent a lot of time on looking at database solutions recently, reading through Jepsen reports and thinking about software architectures. The problem with PostgreSQL is that it is essentially a single-point-of-failure solution (yes, I do know about various replication scenarios and solutions, in fact I learned much more about them than I ever wanted to know). This is perfectly fine for many applications, but not nearly enough to call it "the world's best database".
Re: PostgreSQL is the worlds’ best database
#26Earlier quoted context omitted.
Here's the last line of my post: "Not that I'm knocking PG, 'best' depends upon the problem" I did not want to get into a war with people emotionally involved in their favourite programming tool. The article said 'best'. By that measure PG was worse. Point is it doesn't matter, it's about what problem you are trying to solve and at what price. In many cases PG is best for that - do you understand? I knew people would…
You do realize you are the one getting emotional because you are clinging to an engine that consistently underperforms in benchmarks across the board and costs you a fortune right? Hope the job security is worth being an expert in a bunch of defunkt practices in 10 years nobody will want.
> consistently underperforms in benchmarks across the board
Show me mssql vs PG speed comparison on a recent industry standard benchmark.
> and costs you a fortune right?
Are you witless enough to think I'm unaware of the wallet-raping, labyrinthine licensing of MSSQL?
> Hope the job security is worth...
Since you apparently can't understand, let me spell it out for you: I've recently installed PG to start learning it because, depending on the problem, it IS the best solution. I do hope you can stop feeling the need to protect your pet software package and undersand these are in the end just tools to solve problems.
Re: PostgreSQL is the worlds’ best database
#27I used PostgreSQL as student and during research and had to switch to Microsoft SQL Server as my company uses that since forever.
For features I used on both, the average quality of the SQL Server implementation is between middling and pathetic (mostly the latter). I cannot recall a single instance where I thought "that's nice" or anything positive about how SQL Server does something. At best, it has been "this is not awful".
Things that sucked especially hard:
- Datetime API: In postgresql it is a joy to use and most features one would like to have to analyze data are directly there and work as they should. The analysis for my master's thesis was completely done in postgresql [1] (including outputting CSV files that could then be used by the LaTeX document) - without ever feeling constrained by the language or its features. Meanwhile, the way to store a Timespan from C# via EF is to convert it to a string and back or convert it to ticks and store it as long.
- The documentation: The pgsql documentation is the best of any project I have ever seen, the one for SQL Server is horrible and doesn't seem to have any redeeming qualities. - Management: SMSS is a usability nightmare and still the recommended choice for doing anything. I assume there are better ways but I haven't found them and if I have, they usually didn't work.
- The query language: In psql you can do things like
select a select case when a Maybe my use cases are a bit weird and I haven't encountered the better features of SQL Server yet. Would appreciate if someone could point out what I am doing wrong.
[1]: https://github.com/oerpli/MONitERO/blob/master/sql/queries/r...
Re: PostgreSQL is the worlds’ best database
#28Let’s say I have a table for reservations: 1. Item ID 2. Reservation duration
What I would like is if I have an item ID of 1 and a reservation duration of today 10AM to 11AM and I try to add another record of item ID 1 and duration 10:39AM to 11:39AM the insert should fail.
Apparently it is straightforward in db2 but not in postgresql?
Re: PostgreSQL is the worlds’ best database
#29My first job in IT, I was 18, it was the early 2000s. I was a nerd but in professional IT I was essentially a blank slate.
I lucked up and ended up with a real hacker for a boss. As early as 2001-2002 he had saved entire businesses by migrating them from mysql to postgres.
He was a BSD guy and a postgres guy. He made me into a fanboy of both those technologies.
So out of sheer luck I've preferred Postgres for over 15 years, and it has never disappointed me.
Unlike BSD, which often disappointed me once I learned how much easier and mature Linux was to use.
Re: PostgreSQL is the worlds’ best database
#30Let’s say I have a table for reservations: 1. Item ID 2. Reservation duration What I would like is if I have an item ID of 1 and a reservation duration of today 10AM to 11AM and I try to add another record of item ID 1 and duration 10:39AM to 11:39AM the insert should fail. Apparently it is straightforward in db2 but not in postgresql?
Postgresql supports storing range of values, in particular ranges of timestamps.
I never used them but the manual page shows an example on avoiding overlaps that looks a lot like your case:
https://www.postgresql.org/docs/12/rangetypes.html#RANGETYPE...