Oh how I wish for Postgres to introduce system-versioned (bi-temporal) tables.
PostgreSQL 17
51–60 of 153 posts
Re: PostgreSQL 17
#52MERGE support for updating views is huge. So looking forward to this
Now it also supports RETURNS keyword !
Re: PostgreSQL 17
#53Earlier quoted context omitted.
MS Azure SQL on is very cheap compared to any other self hosted database including PG and MS SQL. Unless they running a super heavy workload , this solution will meet most business requirements. But this is also a gateway drug for cloud addiction.
After scanning the Azure and AWS pricing pages and calculators for comparably speced Azure Manged SQL and Amazon RDS for PostgreSQL instances, AWS's RDS comes out at about 1/3 the price of Azure Managed SQL. This matches my experience with deployments on AWS and Azure. Both are managed db instances, but Azure's is consistently more expensive for comparable offerings on AWS or GCP.
Is there any analog for Azure SQL Elastic Pools for Postgres anywhere?
We pay in total something around 600 bucks to manage around 250 databases in MSSQL servers (with failover for prod databases, DTU based model)
We pay for log analytics more then we pay for Sql Servers.
Those Elastic Pools is a blocker for us on the way to migrate to Postgres from MSSQL...
Re: PostgreSQL 17
#54Earlier quoted context omitted.
I got my start in a SQLserver all MS shop. I hated SSIS. I wished I just had something akin to Python and dataframes to just parse things in a data pipeline. Instead I had some graphical tool whose error messages and deployments left a lot to be desired. But SQLServer and Microsoft in general make for good platforms for companies: they’re ubiquitous enough that you won’t find it hard to find engineers to work on your…
The key feature of SSIS, is parallel dataflow You can so easily write (and schedule) parallel dataflows in SSIS, to do the same code using a general purpose programming language would be a lot harder Also remember that dataflows are data pipe streams, so SSIS can be very very fast Anyway, there is BIML, which allow you to create SSIS package by writing XML, I personally never used it, mainly because its licensing sit…
Yeah I think I never gave it a fair shake. I think — like most things — if understood and used properly it can be amazing.
Re: PostgreSQL 17
#55Very impressive changelog. Bit sad the UUIDv7 PR didn't make the cut just yet: https://commitfest.postgresql.org/49/4388/
I've been waiting for "incremental view maintenance" (i.e. incremental updates for materialized views) but it looks like it's still a few years out.
There's always the pg_ivm extension you can use in the meantime: https://github.com/sraoss/pg_ivm
Re: PostgreSQL 17
#56Earlier quoted context omitted.
MS Azure SQL on is very cheap compared to any other self hosted database including PG and MS SQL. Unless they running a super heavy workload , this solution will meet most business requirements. But this is also a gateway drug for cloud addiction.
After scanning the Azure and AWS pricing pages and calculators for comparably speced Azure Manged SQL and Amazon RDS for PostgreSQL instances, AWS's RDS comes out at about 1/3 the price of Azure Managed SQL. This matches my experience with deployments on AWS and Azure. Both are managed db instances, but Azure's is consistently more expensive for comparable offerings on AWS or GCP.
I do not have experience with AWS RDS so I cannot speak to that.
In my experience, GCP Cloud SQL for Postgres has been more expensive than MS Azure SQL. In our tests, CloudSQL also was not comparable to the resiliency offered by Azure SQL. Things like Automated DR and automated failover etc. were not at par with what Azure offered. Not to mention , Column level encryption is standard for Azure SQL.
Re: PostgreSQL 17
#57With 17, is Vacuum largely a solved issue?
There was a big project to re-architect the low level storage system to something that isn't dependent on vacuuming, called zheap. Unfortunately it seems to have stalled and nobody seems to be working on it anymore? I keep scanning the release notes for each new pgsql version, but no dice.
I think OrioleDB is picking up from where zheap left things, and seems quite active in upstreaming their work, you might be interested to check it out.
Re: PostgreSQL 17
#58Earlier quoted context omitted.
I've been waiting for "incremental view maintenance" (i.e. incremental updates for materialized views) but it looks like it's still a few years out.
There's always the pg_ivm extension you can use in the meantime: https://github.com/sraoss/pg_ivm
Unfortunately we use a cloud provider to host our databases, so I can only install limited extensions.
Re: PostgreSQL 17
#59With 17, is Vacuum largely a solved issue?
No, vacuum issues are not solved. This will reduce the amount of scanning needed in many cases when vacuuming indexes. It will mean more efficient vacuum and quicker vacuums which will help in a lot of cases.
Re: PostgreSQL 17
#60Oh how I wish for Postgres to introduce system-versioned (bi-temporal) tables.
What's your use case for system-versioned tables? You could use some extensions like Periods that support bi-temporal tables: https://wiki.postgresql.org/wiki/Temporal_Extensions
Or you could use triggers to build one: https://hypirion.com/musings/implementing-system-versioned-t...