[HN Gopher] PostgreSQL Subtransactions Considered Harmful ___________________________________________________________________ PostgreSQL Subtransactions Considered Harmful Author : samokhvalov Score : 12 points Date : 2021-08-31 22:14 UTC (46 minutes ago) (HTM) web link (postgres.ai) (TXT) w3m dump (postgres.ai) | justinludwig wrote: | Lame title, but a really good, in-depth examination of the | lurking issues with subtransactions on postgres. | monkey26 wrote: | Really dislike these "considered harmful" type titles. | ahachete wrote: | This is a deep and excellent post. Thanks for publishing it and | all the research required. | | Maybe too much 30,000 feet perspective, but in general everything | that is "state" in a session is a potential limit to performance | and scalability. | | In this blog post, it is the "state" associated with | subtransactions. In another area, it may be Prepared Statements. | Often regarded as better performing than non prepared (and they | strictly are, generally), they impose hard limits into connection | scalability. Connection poolers cannot hold this state and thus | you cannot use transaction pooling, which boosts performance and | resource usage much more than prepared vs non-prepared. | | Anyway, that's another topic. But session state --is something | I'm becoming more and more against. YMMV. ___________________________________________________________________ (page generated 2021-08-31 23:00 UTC)