| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | "Bandi, Venkataramana - Dell Team" <Venkataramana(dot)Bandi(at)dellteam(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Cc: | "Kishore, Nanda - Dell Team" <Nanda(dot)Kishore(at)Dellteam(dot)com>, "Alampalli, Kishore" <Kishoreravishankar(dot)Alampalli(at)dellteam(dot)com> |
| Subject: | Re: Query on Postgres SQL transaction |
| Date: | 2024-03-15 17:42:34 |
| Message-ID: | 48ea6606-41ad-4094-887a-466c8c827bf2@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3/14/24 11:04 PM, Bandi, Venkataramana - Dell Team wrote:
>
> Hi Team,
>
> We are using JPA entities to persists the records into Postgres SQL DB
> and its working for all the nodes but one of the node data is not
> persisting and it’s not giving any DB related errors/exception. We
> just want to trace out this scenario on transaction level whether
> transaction is committing or not.
>
"... its working for all the nodes but one of the node data is not
persisting ..." contradict.
Generally when a record does not throw an error, but is not persisted it
means the transaction was not committed and the changes did not survive
the session they where done in. Without the actual code it hard to say
anything more.
> Could you please let us know how we can trace out this scenario and
> let us know how transaction logs enabled in Postgres SQL DB.
>
> Regards,
>
> Venkat
>
>
> Internal Use - Confidential
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vedant patel | 2024-03-15 17:58:01 | Re: PostGres ODBC too slow |
| Previous Message | Adrian Klaver | 2024-03-15 17:39:20 | Re: PostGres ODBC too slow |