Look, this announcement seemed exciting, but I'm significantly less excited when I come across a completely unrelated tie-in to AI.
It breaks the illusion, and I'm reminded that it's just another PR announcement, and this is probably not going to impact my life at all in any way ever. So I'm off to the next article instead of reading any more.
Curious how is the final format of the data in LTAP storage - is it columnar? If so then what happens to OLTP performance - the blog and all info speaks to OLAP performance but what about your app
> No performance tradeoffs, for any workload: Transactional workloads run in standard Postgres with full ACID semantics. Analytical workloads run across the full Lakehouse at any scale and concurrency. Each scales independently, and because there's no data movement between systems, operational and analytical results are always in sync — with no copies or shadow infrastructure.
How can there be no performance trade-off if storage is handled by PostGres and there is no data movement to convert it to columnar ?
This deserve a technical explanation because this seems impossible.
6 comments
[ 3.4 ms ] story [ 21.5 ms ] threadLook, this announcement seemed exciting, but I'm significantly less excited when I come across a completely unrelated tie-in to AI.
It breaks the illusion, and I'm reminded that it's just another PR announcement, and this is probably not going to impact my life at all in any way ever. So I'm off to the next article instead of reading any more.
How can there be no performance trade-off if storage is handled by PostGres and there is no data movement to convert it to columnar ? This deserve a technical explanation because this seems impossible.