logoalt Hacker News

jeltzlast Thursday at 10:55 PM3 repliesview on HN

Ok ... you know PostgreSQL supports hash tables in shared memory, right? PostgreSQL could in theory share those if we wanted to. The issue is just that coding anything which uses shared memory is a lot of work.

Additionally the reasons PostgreSQL does not offer Clickhouse performance has very little to do with parallelism. PostgreSQL plans to move to threading but the efforts around imporving OLAP performance are almost entirely unrelated.


Replies

comexyesterday at 4:41 AM

> The issue is just that coding anything which uses shared memory is a lot of work.

Doesn’t that kind of prove the parent’s point though? In theory shared memory can do anything that threads can do. But if in practice some feature doesn’t get implemented in the multi-process design (because shared memory is hard), when it likely would have been implemented in a threaded design, then that’s still an advantage for threads.

gpmyesterday at 12:54 AM

Apart from being a lot of work are you really gaining much at that point? Memory corruption can still take down both sides...

dupontcyborgyesterday at 12:01 AM

i may be missing context, but shared memory across processes, without ipc?

show 2 replies