The Postgres team seems fairly good at not being afraid to tackle its weaknesses and pain points. They recently worked on eliminating vacuum. But Postgres has a serious PgBouncer problem. It would be _really_ nice if the removing that pain point would get on the roadmap.
-
-
Replying to @kellabyte
Good news: there is already a (long) discussion on moving connection pooling into the core software: https://www.postgresql.org/message-id/flat/4b971a8f-ff61-40eb-8f30-7b57eb0fdf9d%40postgrespro.ru …
1 reply 4 retweets 10 likes -
Replying to @kellabyte @jkatz05
Yup! I believe that's the thread where I learned that the query parallelization work could make it easier.
1 reply 0 retweets 0 likes -
How the heck do you guys keep up with all this stuff?
1 reply 0 retweets 1 like -
Replying to @kellabyte @rbranson
The most common answer is "We can't read everything." :-) Personally, I try to at least skim the headlines on pgsql-hackers; read through threads where I need more details; see/listen what people are saying; ask around. And then test myself by writing news releases ;-)
1 reply 0 retweets 2 likes -
Yeah I think even our most area-covering developers have given up on reading everything by now. There was a time when that was possible, but not anymore.
1 reply 0 retweets 1 like
I hacked up my copy of mutt so I can mark threads as auto-read for a while...
-
-
Replying to @AndresFreundTec @magnushagander and
I'm surprised that this feature is not yet included in mutt...
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.