Re: Is replacing transactions with CTE a good idea?

From: Glen Huang <heyhgl(at)gmail(dot)com>
To: Dave Cramer <davecramer(at)postgres(dot)rocks>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Is replacing transactions with CTE a good idea?
Date: 2021-04-01 15:09:27
Message-ID: 75F6F752-5A32-46AC-B314-28403915DBA2@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

No, but are they equivalent to serializable transactions?

> On Apr 1, 2021, at 11:04 PM, Dave Cramer <davecramer(at)postgres(dot)rocks> wrote:
>
> 
>
>
>
>> On Thu, 1 Apr 2021 at 10:50, Glen Huang <heyhgl(at)gmail(dot)com> wrote:
>> 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 them back 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 in parallel?
>
> I do not think a CTE changes the isolation level.
>>
>> If I decide to replace all my transaction code with CTE, will I shoot myself in the foot down the road?
>
>
> Dave Cramer
> www.postgres.rocks

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dave Cramer 2021-04-01 15:10:23 Re: Is replacing transactions with CTE a good idea?
Previous Message Glen Huang 2021-04-01 15:06:32 Re: Is replacing transactions with CTE a good idea?