From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Glen Huang <heyhgl(at)gmail(dot)com> |
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:10:23 |
Message-ID: | CADK3HHLzbbn0EQg_rgL8iiro-LZT6fG7rHdp_WW5uB36aJKspQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 1 Apr 2021 at 11:09, Glen Huang <heyhgl(at)gmail(dot)com> wrote:
> No, but are they equivalent to serializable transactions?
>
No, they are not.
Dave Cramer
www.postgres.rocks
>
> 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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Glen Huang | 2021-04-01 15:20:45 | Re: Is replacing transactions with CTE a good idea? |
Previous Message | Glen Huang | 2021-04-01 15:09:27 | Re: Is replacing transactions with CTE a good idea? |