Is replacing transactions with CTE a good idea? - Mailing list pgsql-general

From Glen Huang
Subject Is replacing transactions with CTE a good idea?
Date
Msg-id DED55D28-088A-432E-B961-15567A5BD1CC@gmail.com
Whole thread Raw
Responses Re: Is replacing transactions with CTE a good idea?  (Brian Dunavant <dunavant@gmail.com>)
Re: Is replacing transactions with CTE a good idea?  (Dave Cramer <davecramer@postgres.rocks>)
List pgsql-general
Hi all,

From application’s standpoint, it seems using CTE saves a lot work. You no longer need to parse values out only to pass
themback in, and only one round-trip to the db server. 

If I’m not wrong, CTE is equivalent to serializable transactions? So I guess the downsize is that quarries can’t be run
inparallel? 

If I decide to replace all my transaction code with CTE, will I shoot myself in the foot down the road?


pgsql-general by date:

Previous
From: Glen Huang
Date:
Subject: Re: How to implement expiration in PostgreSQL?
Next
From: Brian Dunavant
Date:
Subject: Re: Is replacing transactions with CTE a good idea?