From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Dominique Devienne <ddevienne(at)gmail(dot)com>, veem v <veema0000(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Moving to Postgresql database |
Date: | 2024-01-16 16:07:52 |
Message-ID: | 40a34680-1583-4cff-86cb-2598be16bb80@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/16/24 00:06, Dominique Devienne wrote:
> On Mon, Jan 15, 2024 at 5:17 AM veem v <veema0000(at)gmail(dot)com
> <mailto:veema0000(at)gmail(dot)com>> wrote:
>
> Is any key design/architectural changes should the app development
> team [...], should really aware about
>
>
> Hi. One of the biggest pitfall of PostgreSQL, from the app-dev perspective,
> is the fact any failed statement fails the whole transaction, with
> ROLLBACK as the only recourse.
https://www.postgresql.org/docs/current/sql-savepoint.html
"SAVEPOINT establishes a new savepoint within the current transaction.
A savepoint is a special mark inside a transaction that allows all
commands that are executed after it was established to be rolled back,
restoring the transaction state to what it was at the time of the
savepoint."
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Bablu Kumar Nayak | 2024-01-16 16:29:25 | Postgres Database Service Interruption |
Previous Message | Sasmit Utkarsh | 2024-01-16 15:09:52 | Re: Help needed for the resolution of memory leak |