Re: a path towards replacing GEQO with something better

Hi, I stumbled across this which may be of interest to this topic and GEQO alternative. The main creator/author of Neo and Bao (ML for Query Optimizer) Ryan Marcus (finishing Postdoc and looking for job) recently posted [1] about Bao for distributed systems. But what was interesting was

Re: Improving connection scalability: GetSnapshotData()

Hi, Greatly appreciate if you could please reply to the following questions as time allows. I have seen previous discussion/patches on a built-in connection pooler. How does this scalability improvement, particularly idle connection improvements etc, affect that built-in pooler need, if any? Sa

Re: LSM tree for Postgres

Dmitry Dolgov wrote >> On Tue, Aug 04, 2020 at 11:22:13AM +0300, Konstantin Knizhnik wrote: >> >> Then I think about implementing ideas of LSM using standard Postgres >> nbtree. >> >> We need two indexes: one small for fast inserts and another - big >> (main) index. This top index is small enough t

Re: Is zheap on track for PostgreSQL 12.0?

Hopefully someone checked out this academic paper, as the perf gains seem impressive on the surface.. http://madsys.cs.tsinghua.edu.cn/publications/TS2018-liu.pdf DudeTx: Durable Transactions Made Decoupled "This paper presents DudeTx, a crash-consistent durable transaction system that avoids th

Re: Global shared meta cache

Ideriha, Takeshi wrote > 2) benchmarked 3 times for each conditions and got the average result of > TPS. > |master branch | prototype | > proto/master (%) > > >pgben

Re: Pluggable storage

@Amit Re: Vacuum etc. Chrome V8 just released this blog post around concurrent marking, which may be of interest considering how cpu limited the browser is. Contains benchmark numbers etc in post as well. https://v8project.blogspot.com/2018/06/concurrent-marking.html "This post describes the ga

Re: Column store in Greenplum

Please consider other Dbs like ClickHouse as well :) Im hoping PG one day performs 80% as well as these so no need to use them in first instance. -- Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html

Re: Interesting paper: Contention-Aware Lock Scheduling

Another interesting article from Jan 2018 (Tsinghua University and Microsoft Research) http://madsys.cs.tsinghua.edu.cn/publications/TS2018-liu.pdf DudeTx: Durable Transactions Made Decoupled "This paper presents DudeTx, a crash-consistent durable transaction system that avoids the drawbacks of