undefined | Better HN

0 pointsdeadbabe1mo ago0 comments

LISTEN/NOTIFY is not brittle, we use it for millions of events per day.

0 comments

I agree! It should be very stable, IMO. If not, then please send a bug report and we'll look into it. Also, now it scales well with the number of listening connections (given clients listen on unique channel names): https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...

deadbabeOP1mo ago

The LISTEN/NOTIFY feature really just doesn’t get enough PR. It is perfectly suitable for production workloads yet people still want to reach for more complicated solutions they don’t need.

figassis1mo ago

It's not the feature itself, it's how/what the llm tries to use it for. It uses it to cross any and all architectural boundaries.

j / k navigate · click thread line to collapse

0 comments

JoelJacobson1mo ago

deadbabeOP1mo ago

The LISTEN/NOTIFY feature really just doesn’t get enough PR. It is perfectly suitable for production workloads yet people still want to reach for more complicated solutions they don’t need.

figassis1mo ago

It's not the feature itself, it's how/what the llm tries to use it for. It uses it to cross any and all architectural boundaries.

j / k navigate · click thread line to collapse