Earlier quoted context omitted.
Out of interest ;) SQL Server is such an expensive beast, ~$15K per core, what are your reasons for prefering it over PG?
I quite like Postgres and use it preferentially, but your numbers are off. SQL Server Enterprise costs more like $7500/core; that $15K pack, as far as I am aware, comes with two core licenses. SQL Server Standard 2016 costs $931 for a license if you use CALs ($209 a pop), or $3700/core. Also bear in mind that almost nobody pays list price for any of this.
PostgreSQL 11.3 and 10.8
41–50 of 162 posts
Re: PostgreSQL 11.3 and 10.8
#42It's hard to believe that Google Cloud SQL still only has 9.6 available. EDIT: Apparently 11.1 is available in beta as of April 9th.
Actually, 11 is now in Beta. If you create a new instance it is listed as an option.
EDIT: I'll try again. Looks like it was added April 9th
Re: PostgreSQL 11.3 and 10.8
#43Question for PG happy users. How do you manage failover and replication? At my previous job this was done by a consultant. Is this doable on a self hosted setup? Thank you in advance.
Re: PostgreSQL 11.3 and 10.8
#44Re: PostgreSQL 11.3 and 10.8
#45I'm not a database guy so have no clue, but why are there so many versions receiving support? Is there just that much legacy crap they can't get away from, like Python?
2) It's horrifically high risk because downgrading is usually not a thing
3) It usually requires downtime.
Re: PostgreSQL 11.3 and 10.8
#46Earlier quoted context omitted.
Out of interest (SQL Server guy mainly, so only partly keep up with what other engines are doing), what changes significantly affect performance (without making changes to your own code/configuration to make use of new features) in 10.x & 11.x?
It kinda bugs me that people say "SQL Server" to mean "Microsoft SQL Server". I mean, there are other sql servers.
Re: PostgreSQL 11.3 and 10.8
#47For a complex web-app, would you suggest an ORM (looking at SQLAlchemy) or a custom module with hand written queries and custom methods for conversion to python objects?
My app has a lot of complex queries, joins, etc. and the data-model is most likely to change quite a bit as the app nears production. I feel using an ORM is an unnecessary layer of abstraction in the thinking process. I feel comfortable with direct SQL queries, and in some cases, want to directly get JSON results from PGSQL itself.
Would that be a good idea, and more importantly, scalable?
Note : My app will be solely developed by me, not expecting to have a team or even another developer work on it.
Re: PostgreSQL 11.3 and 10.8
#48Totally wish we could upgrade but for some reason AWS have still not implemented any upgrade path for Aurora PostgreSQL other than dump and reimport despite apparently working on it for a year...
Does AWS Aurora actually use postgres or is it simply a postgres compatible API on top of their own technology?
Re: PostgreSQL 11.3 and 10.8
#49Earlier quoted context omitted.
Out of interest (SQL Server guy mainly, so only partly keep up with what other engines are doing), what changes significantly affect performance (without making changes to your own code/configuration to make use of new features) in 10.x & 11.x?
It kinda bugs me that people say "SQL Server" to mean "Microsoft SQL Server". I mean, there are other sql servers.
I don't mind that; sure, there are other RDBMS servers that support SQL as their main or exclusive language, but unless you are talking about ancient Sybase products (for which there is a very good reason for the shared branding) “SQL Server” is a clear, exclusive Microsoft product identity and not any worse of a label, say, FTP (yes, there are other file transfer protocols).
OTOH,what does bug me is when people say “SQL” to mean “Microsoft SQL Server”.
Re: PostgreSQL 11.3 and 10.8
#50Question for PG happy users. How do you manage failover and replication? At my previous job this was done by a consultant. Is this doable on a self hosted setup? Thank you in advance.