Re: Query on Postgres SQL transaction
On 3/30/24 03:14, Bandi, Venkataramana - Dell Team wrote: Hi, Clarifying the problem statement again, Multiple requests are getting to our application server and using hibernate framework to persist the data into Postgres SQL DB but for one of the request, it is also similar request like other requests and there are no differences b/w these requests in terms of different OS, different network etc. but data is not persisting few times. You have fallen into the trap of working the problem(repeating the problem definition) instead of working the solution, taking the steps to solve it. Start with acknowledging that this "...there are no differences b/w these requests ..." is not the case, otherwise we would not be having this discusion. This is going to involve working through the process from the front end to the database. Start with: How do you know which data is not persisting? Did the INSERT entry you show below persist? We have enabled below properties in postgresql.conf file and verified but didn't get any findings about the transaction and below log statements are writing in our data store logs. log_statement = 'all' logging_collector = on log_min_messages = debug5 log_min_error_statement = debug5 2024-02-19 15:21:54.850 +08 [1876] LOG: execute S_48: insert into xxx (f_schedule_name,f_id,f_totaldataredtn,f_invalidationtime,f_statuscode,f_module,f_app_type,f_dbbackuptype,f_is_compressed,f_proxy,f_size,f_sizeprotected,f_groupjobid,f_status,f_bytesmodifiednotsent,f_sizetransferredboffset,f_bytesmodifiedsent,f_errcode,f_jobid2,f_media_server,f_starttime,f_storageid,f_pool,f_queuestart,f_sizescannedboffset,f_errorcodesummary,f_ncopies,f_sizeprotectedboffset,f_snap_target_platform,f_backup_servername,f_nfiles,f_expiry,f_owner,f_policy_id,f_parentjobid,f_sub_name,f_completion_status,f_endtime,f_filesscanned,f_idle_wait,f_storage_unit,f_group_id,f_backup_set,f_ntries,f_job_name,f_level,f_agent_name,f_failed_copies,f_restarted_job,f_success_copies,f_domain_id,f_snap_target,f_jobid,f_request_id,f_pluginname,f_sizetransferred,f_is_snap,f_node_id,f_workflow_id,f_action_name,f_agent_id,f_instancename,f_session,f_totalobjdedup,f_changedbytes,f_sizeboffset,f_dedupredtn,f_statuscodesummary,f_workflow_jobid,f_snap_policy,f_size_copies,f_sizescanned,f_sub_id,f_archive_flag,f_nfilesnot,f_media_wait,f_snap_creation,f_effective_path) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42,$43,$44,$45,$46,$47,$48,$49,$50,$51,$52,$53,$54,$55,$56,$57,$58,$59,$60,$61,$62,$63,$64,$65,$66,$67,$68,$69,$70,$71,$72,$73,$74,$75,$76,$77,$78) 2024-02-19 15:21:54.851 +08 [10928] DEBUG: bind to 2024-02-19 15:21:54.852 +08 [10928] DEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0 Could you let us know any other way to trace out these kind of DB transactions? Regards, Venkat Internal Use - Confidential -Original Message- From: Adrian Klaver Sent: Wednesday, March 27, 2024 9:32 PM To: Bandi, Venkataramana - Dell Team ; Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] On 3/27/24 04:29, Bandi, Venkataramana - Dell Team wrote: Hi, As l already mentioned, for this specific node also data is persisting but sometimes(randomly) data is not persisting. How do you know which data is not persisting? As you mentioned our application doesn't have any restrictions on OS level and on network etc. different OS or OS version, different encoding, different location on the network, different data it is working, etc. I don't understand what the above is saying. Do you mean there are differences in these attributes between the nodes or no differences? Also please do not top post, use either bottom or inline posting per: https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Posting_style__;!!LpKI!glyl28rP3t6cLe3s9tF3X5_4YU28-qPJsOaPHUjX9F01s4DCAXmZVedjlyKpvXlv-TgG-800u0Drq4lWC2f8CObdQX3ijBWevQ$ [en[.]wikipedia[.]org] Regards, Venkat -- Adrian Klaver adrian.kla...@aklaver.com -- Adrian Klaver adrian.kla...@aklaver.com
RE: Query on Postgres SQL transaction
Hi, Clarifying the problem statement again, Multiple requests are getting to our application server and using hibernate framework to persist the data into Postgres SQL DB but for one of the request, it is also similar request like other requests and there are no differences b/w these requests in terms of different OS, different network etc. but data is not persisting few times. We have enabled below properties in postgresql.conf file and verified but didn't get any findings about the transaction and below log statements are writing in our data store logs. log_statement = 'all' logging_collector = on log_min_messages = debug5 log_min_error_statement = debug5 2024-02-19 15:21:54.850 +08 [1876] LOG: execute S_48: insert into xxx (f_schedule_name,f_id,f_totaldataredtn,f_invalidationtime,f_statuscode,f_module,f_app_type,f_dbbackuptype,f_is_compressed,f_proxy,f_size,f_sizeprotected,f_groupjobid,f_status,f_bytesmodifiednotsent,f_sizetransferredboffset,f_bytesmodifiedsent,f_errcode,f_jobid2,f_media_server,f_starttime,f_storageid,f_pool,f_queuestart,f_sizescannedboffset,f_errorcodesummary,f_ncopies,f_sizeprotectedboffset,f_snap_target_platform,f_backup_servername,f_nfiles,f_expiry,f_owner,f_policy_id,f_parentjobid,f_sub_name,f_completion_status,f_endtime,f_filesscanned,f_idle_wait,f_storage_unit,f_group_id,f_backup_set,f_ntries,f_job_name,f_level,f_agent_name,f_failed_copies,f_restarted_job,f_success_copies,f_domain_id,f_snap_target,f_jobid,f_request_id,f_pluginname,f_sizetransferred,f_is_snap,f_node_id,f_workflow_id,f_action_name,f_agent_id,f_instancename,f_session,f_totalobjdedup,f_changedbytes,f_sizeboffset,f_dedupredtn,f_statuscodesummary,f_workflow_jobid,f_snap_policy,f_size_copies,f_sizescanned,f_sub_id,f_archive_flag,f_nfilesnot,f_media_wait,f_snap_creation,f_effective_path) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42,$43,$44,$45,$46,$47,$48,$49,$50,$51,$52,$53,$54,$55,$56,$57,$58,$59,$60,$61,$62,$63,$64,$65,$66,$67,$68,$69,$70,$71,$72,$73,$74,$75,$76,$77,$78) 2024-02-19 15:21:54.851 +08 [10928] DEBUG: bind to 2024-02-19 15:21:54.852 +08 [10928] DEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0 Could you let us know any other way to trace out these kind of DB transactions? Regards, Venkat Internal Use - Confidential -Original Message- From: Adrian Klaver Sent: Wednesday, March 27, 2024 9:32 PM To: Bandi, Venkataramana - Dell Team ; Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] On 3/27/24 04:29, Bandi, Venkataramana - Dell Team wrote: > Hi, > > As l already mentioned, for this specific node also data is persisting but > sometimes(randomly) data is not persisting. How do you know which data is not persisting? > > As you mentioned our application doesn't have any restrictions on OS level > and on network etc. > > different OS or OS version, different encoding, different location on the > network, different data it is working, etc. I don't understand what the above is saying. Do you mean there are differences in these attributes between the nodes or no differences? Also please do not top post, use either bottom or inline posting per: https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Posting_style__;!!LpKI!glyl28rP3t6cLe3s9tF3X5_4YU28-qPJsOaPHUjX9F01s4DCAXmZVedjlyKpvXlv-TgG-800u0Drq4lWC2f8CObdQX3ijBWevQ$ [en[.]wikipedia[.]org] > > Regards, > Venkat > -- Adrian Klaver adrian.kla...@aklaver.com
Re: Query on Postgres SQL transaction
That log snippet shows two different PIDs. Check the logs to see the
complete path that process 1876 took after it did the insert at 2024-02-19
15:21:54.850 +08
Make sure you are not using prepared transactions. This should return 0:
select current_setting('max_prepared_transactions');
Cheers,
Greg
Re: Query on Postgres SQL transaction
On 3/27/24 04:29, Bandi, Venkataramana - Dell Team wrote: Hi, As l already mentioned, for this specific node also data is persisting but sometimes(randomly) data is not persisting. How do you know which data is not persisting? As you mentioned our application doesn't have any restrictions on OS level and on network etc. different OS or OS version, different encoding, different location on the network, different data it is working, etc. I don't understand what the above is saying. Do you mean there are differences in these attributes between the nodes or no differences? Also please do not top post, use either bottom or inline posting per: https://en.wikipedia.org/wiki/Posting_style Regards, Venkat -- Adrian Klaver adrian.kla...@aklaver.com
RE: Query on Postgres SQL transaction
Hi, As l already mentioned, for this specific node also data is persisting but sometimes(randomly) data is not persisting. As you mentioned our application doesn't have any restrictions on OS level and on network etc. different OS or OS version, different encoding, different location on the network, different data it is working, etc. Regards, Venkat Internal Use - Confidential -Original Message- From: Bandi, Venkataramana - Dell Team Sent: Wednesday, March 27, 2024 10:18 AM To: Adrian Klaver ; Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: RE: Query on Postgres SQL transaction Hi Adrian, I will check with the customer on below info for that node and will share you. For instance different OS or OS version, different encoding, different location on the network, different data it is working, etc. As I already mentioned we have enabled Postgres SQL debug logs to trace out this scenario, but it is not helping us. Regards, Venkat -Original Message- From: Adrian Klaver Sent: Monday, March 25, 2024 8:40 PM To: Bandi, Venkataramana - Dell Team ; Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] On 3/25/24 00:18, Bandi, Venkataramana - Dell Team wrote: > Hi, > > Please find my inline comments for your questions. > > > Regards, > Venkat > > > Internal Use - Confidential > -Original Message- > From: Adrian Klaver > Sent: Tuesday, March 19, 2024 9:33 PM > To: Bandi, Venkataramana - Dell Team > ; Greg Sabino Mullane > > Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team > ; Alampalli, Kishore > > Subject: Re: Query on Postgres SQL transaction > > > [EXTERNAL EMAIL] > > On 3/19/24 02:18, Bandi, Venkataramana - Dell Team wrote: >> Hi Greg, >> >> We are using hibernate framework to persist the data into Postgres >> SQL DB and data is persisting and committing for all the clients but >> one of the client data is not inserted into DB. > > What is different about that client? > Ans: In our application data is getting from different nodes(systems) and > persisting into Postgres SQL DB but for one of the nodes(system) data is not > persisting and sometimes data is persisting for this node also. We have to > trace out the transaction why data is not persisting sometimes. That we knew already. What I was after was whether that particular node(system) is different in some important way from the others. For instance different OS or OS version, different encoding, different location on the network, different data it is working, etc. Define what you have done to trace the path of the transaction. > Are all the clients passing data through the same instance of the framework? > Ans: Since it is a monolithic architecture application, it is running on same > instance. > Are you sure that the client is pointed at the correct database? > Ans: Yes, its pointed to correct database and with same database connection, > data is persisting for other nodes. > Is the log entry below from that client? > Ans: Yes >> -- Adrian Klaver adrian.kla...@aklaver.com
RE: Query on Postgres SQL transaction
Hi Adrian, I will check with the customer on below info for that node and will share you. For instance different OS or OS version, different encoding, different location on the network, different data it is working, etc. As I already mentioned we have enabled Postgres SQL debug logs to trace out this scenario, but it is not helping us. Regards, Venkat Internal Use - Confidential -Original Message- From: Adrian Klaver Sent: Monday, March 25, 2024 8:40 PM To: Bandi, Venkataramana - Dell Team ; Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] On 3/25/24 00:18, Bandi, Venkataramana - Dell Team wrote: > Hi, > > Please find my inline comments for your questions. > > > Regards, > Venkat > > > Internal Use - Confidential > -Original Message- > From: Adrian Klaver > Sent: Tuesday, March 19, 2024 9:33 PM > To: Bandi, Venkataramana - Dell Team > ; Greg Sabino Mullane > > Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team > ; Alampalli, Kishore > > Subject: Re: Query on Postgres SQL transaction > > > [EXTERNAL EMAIL] > > On 3/19/24 02:18, Bandi, Venkataramana - Dell Team wrote: >> Hi Greg, >> >> We are using hibernate framework to persist the data into Postgres >> SQL DB and data is persisting and committing for all the clients but >> one of the client data is not inserted into DB. > > What is different about that client? > Ans: In our application data is getting from different nodes(systems) and > persisting into Postgres SQL DB but for one of the nodes(system) data is not > persisting and sometimes data is persisting for this node also. We have to > trace out the transaction why data is not persisting sometimes. That we knew already. What I was after was whether that particular node(system) is different in some important way from the others. For instance different OS or OS version, different encoding, different location on the network, different data it is working, etc. Define what you have done to trace the path of the transaction. > Are all the clients passing data through the same instance of the framework? > Ans: Since it is a monolithic architecture application, it is running on same > instance. > Are you sure that the client is pointed at the correct database? > Ans: Yes, its pointed to correct database and with same database connection, > data is persisting for other nodes. > Is the log entry below from that client? > Ans: Yes >> -- Adrian Klaver adrian.kla...@aklaver.com
Re: Query on Postgres SQL transaction
On 3/25/24 00:18, Bandi, Venkataramana - Dell Team wrote: Hi, Please find my inline comments for your questions. Regards, Venkat Internal Use - Confidential -Original Message- From: Adrian Klaver Sent: Tuesday, March 19, 2024 9:33 PM To: Bandi, Venkataramana - Dell Team ; Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] On 3/19/24 02:18, Bandi, Venkataramana - Dell Team wrote: Hi Greg, We are using hibernate framework to persist the data into Postgres SQL DB and data is persisting and committing for all the clients but one of the client data is not inserted into DB. What is different about that client? Ans: In our application data is getting from different nodes(systems) and persisting into Postgres SQL DB but for one of the nodes(system) data is not persisting and sometimes data is persisting for this node also. We have to trace out the transaction why data is not persisting sometimes. That we knew already. What I was after was whether that particular node(system) is different in some important way from the others. For instance different OS or OS version, different encoding, different location on the network, different data it is working, etc. Define what you have done to trace the path of the transaction. Are all the clients passing data through the same instance of the framework? Ans: Since it is a monolithic architecture application, it is running on same instance. Are you sure that the client is pointed at the correct database? Ans: Yes, its pointed to correct database and with same database connection, data is persisting for other nodes. Is the log entry below from that client? Ans: Yes -- Adrian Klaver adrian.kla...@aklaver.com
RE: Query on Postgres SQL transaction
Hi, Please find my inline comments for your questions. Regards, Venkat Internal Use - Confidential -Original Message- From: Adrian Klaver Sent: Tuesday, March 19, 2024 9:33 PM To: Bandi, Venkataramana - Dell Team ; Greg Sabino Mullane Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] On 3/19/24 02:18, Bandi, Venkataramana - Dell Team wrote: > Hi Greg, > > We are using hibernate framework to persist the data into Postgres SQL > DB and data is persisting and committing for all the clients but one > of the client data is not inserted into DB. What is different about that client? Ans: In our application data is getting from different nodes(systems) and persisting into Postgres SQL DB but for one of the nodes(system) data is not persisting and sometimes data is persisting for this node also. We have to trace out the transaction why data is not persisting sometimes. Are all the clients passing data through the same instance of the framework? Ans: Since it is a monolithic architecture application, it is running on same instance. Are you sure that the client is pointed at the correct database? Ans: Yes, its pointed to correct database and with same database connection, data is persisting for other nodes. Is the log entry below from that client? Ans: Yes > > Not getting any error/exception for this case. Could you please let us > know how we can trace out this scenario on transaction level whether > transaction is committing or not? > > We have enabled below properties in postgresql.conf file and verified > but didn't get any findings about the transaction and below log > statements are writing in our data store logs. > > log_statement = 'all' > > logging_collector = on > > log_min_messages = debug5 > > log_min_error_statement = debug5 > > 2024-02-19 15:21:54.850 +08 [1876] LOG: execute S_48: insert into > xxx > (f_schedule_name,f_id,f_totaldataredtn,f_invalidationtime,f_statuscode > ,f_module,f_app_type,f_dbbackuptype,f_is_compressed,f_proxy,f_size,f_s > izeprotected,f_groupjobid,f_status,f_bytesmodifiednotsent,f_sizetransf > erredboffset,f_bytesmodifiedsent,f_errcode,f_jobid2,f_media_server,f_s > tarttime,f_storageid,f_pool,f_queuestart,f_sizescannedboffset,f_errorc > odesummary,f_ncopies,f_sizeprotectedboffset,f_snap_target_platform,f_b > ackup_servername,f_nfiles,f_expiry,f_owner,f_policy_id,f_parentjobid,f > _sub_name,f_completion_status,f_endtime,f_filesscanned,f_idle_wait,f_s > torage_unit,f_group_id,f_backup_set,f_ntries,f_job_name,f_level,f_agen > t_name,f_failed_copies,f_restarted_job,f_success_copies,f_domain_id,f_ > snap_target,f_jobid,f_request_id,f_pluginname,f_sizetransferred,f_is_s > nap,f_node_id,f_workflow_id,f_action_name,f_agent_id,f_instancename,f_ > session,f_totalobjdedup,f_changedbytes,f_sizeboffset,f_dedupredtn,f_st > atuscodesummary,f_workflow_jobid,f_snap_policy,f_size_copies,f_sizesca > nned,f_sub_id,f_archive_flag,f_nfilesnot,f_media_wait,f_snap_creation, > f_effective_path) values > ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$2 > 0,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37, > $38,$39,$40,$41,$42,$43,$44,$45,$46,$47,$48,$49,$50,$51,$52,$53,$54,$5 > 5,$56,$57,$58,$59,$60,$61,$62,$63,$64,$65,$66,$67,$68,$69,$70,$71,$72, > $73,$74,$75,$76,$77,$78) > > 2024-02-19 15:21:54.851 +08 [10928] DEBUG: bind to > > > 2024-02-19 15:21:54.852 +08 [10928] DEBUG: CommitTransaction(1) name: > unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0 > > Regards, > > Venkat > > * > * > > * > > Internal Use - Confidential > > From:*Greg Sabino Mullane > *Sent:* Saturday, March 16, 2024 12:07 AM > *To:* Bandi, Venkataramana - Dell Team > > *Cc:* pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team > ; Alampalli, Kishore > > *Subject:* Re: Query on Postgres SQL transaction > > [EXTERNAL EMAIL] > > That's a very vague question, but you can trace exactly what is > happening by issuing > > SET log_statement = 'all'; > > Ideally at the session level by your application, but can also set it > at the database and user level. If all else fails, set it globally (i.e. > postgresql.conf). Turn it off again as soon as possible, it will make > your logs extremely verbose. But you can track exactly what your > application is doing. > > Cheers, > > Greg > -- Adrian Klaver adrian.kla...@aklaver.com
Re: Query on Postgres SQL transaction
On 3/19/24 02:18, Bandi, Venkataramana - Dell Team wrote: Hi Greg, We are using hibernate framework to persist the data into Postgres SQL DB and data is persisting and committing for all the clients but one of the client data is not inserted into DB. What is different about that client? Are all the clients passing data through the same instance of the framework? Are you sure that the client is pointed at the correct database? Is the log entry below from that client? Not getting any error/exception for this case. Could you please let us know how we can trace out this scenario on transaction level whether transaction is committing or not? We have enabled below properties in postgresql.conf file and verified but didn't get any findings about the transaction and below log statements are writing in our data store logs. log_statement = 'all' logging_collector = on log_min_messages = debug5 log_min_error_statement = debug5 2024-02-19 15:21:54.850 +08 [1876] LOG: execute S_48: insert into xxx (f_schedule_name,f_id,f_totaldataredtn,f_invalidationtime,f_statuscode,f_module,f_app_type,f_dbbackuptype,f_is_compressed,f_proxy,f_size,f_sizeprotected,f_groupjobid,f_status,f_bytesmodifiednotsent,f_sizetransferredboffset,f_bytesmodifiedsent,f_errcode,f_jobid2,f_media_server,f_starttime,f_storageid,f_pool,f_queuestart,f_sizescannedboffset,f_errorcodesummary,f_ncopies,f_sizeprotectedboffset,f_snap_target_platform,f_backup_servername,f_nfiles,f_expiry,f_owner,f_policy_id,f_parentjobid,f_sub_name,f_completion_status,f_endtime,f_filesscanned,f_idle_wait,f_storage_unit,f_group_id,f_backup_set,f_ntries,f_job_name,f_level,f_agent_name,f_failed_copies,f_restarted_job,f_success_copies,f_domain_id,f_snap_target,f_jobid,f_request_id,f_pluginname,f_sizetransferred,f_is_snap,f_node_id,f_workflow_id,f_action_name,f_agent_id,f_instancename,f_session,f_totalobjdedup,f_changedbytes,f_sizeboffset,f_dedupredtn,f_statuscodesummary,f_workflow_jobid,f_snap_policy,f_size_copies,f_sizescanned,f_sub_id,f_archive_flag,f_nfilesnot,f_media_wait,f_snap_creation,f_effective_path) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42,$43,$44,$45,$46,$47,$48,$49,$50,$51,$52,$53,$54,$55,$56,$57,$58,$59,$60,$61,$62,$63,$64,$65,$66,$67,$68,$69,$70,$71,$72,$73,$74,$75,$76,$77,$78) 2024-02-19 15:21:54.851 +08 [10928] DEBUG: bind to 2024-02-19 15:21:54.852 +08 [10928] DEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0 Regards, Venkat * * * Internal Use - Confidential From:*Greg Sabino Mullane *Sent:* Saturday, March 16, 2024 12:07 AM *To:* Bandi, Venkataramana - Dell Team *Cc:* pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore *Subject:* Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] That's a very vague question, but you can trace exactly what is happening by issuing SET log_statement = 'all'; Ideally at the session level by your application, but can also set it at the database and user level. If all else fails, set it globally (i.e. postgresql.conf). Turn it off again as soon as possible, it will make your logs extremely verbose. But you can track exactly what your application is doing. Cheers, Greg -- Adrian Klaver adrian.kla...@aklaver.com
RE: Query on Postgres SQL transaction
Hi Greg, We are using hibernate framework to persist the data into Postgres SQL DB and data is persisting and committing for all the clients but one of the client data is not inserted into DB. Not getting any error/exception for this case. Could you please let us know how we can trace out this scenario on transaction level whether transaction is committing or not? We have enabled below properties in postgresql.conf file and verified but didn't get any findings about the transaction and below log statements are writing in our data store logs. log_statement = 'all' logging_collector = on log_min_messages = debug5 log_min_error_statement = debug5 2024-02-19 15:21:54.850 +08 [1876] LOG: execute S_48: insert into xxx (f_schedule_name,f_id,f_totaldataredtn,f_invalidationtime,f_statuscode,f_module,f_app_type,f_dbbackuptype,f_is_compressed,f_proxy,f_size,f_sizeprotected,f_groupjobid,f_status,f_bytesmodifiednotsent,f_sizetransferredboffset,f_bytesmodifiedsent,f_errcode,f_jobid2,f_media_server,f_starttime,f_storageid,f_pool,f_queuestart,f_sizescannedboffset,f_errorcodesummary,f_ncopies,f_sizeprotectedboffset,f_snap_target_platform,f_backup_servername,f_nfiles,f_expiry,f_owner,f_policy_id,f_parentjobid,f_sub_name,f_completion_status,f_endtime,f_filesscanned,f_idle_wait,f_storage_unit,f_group_id,f_backup_set,f_ntries,f_job_name,f_level,f_agent_name,f_failed_copies,f_restarted_job,f_success_copies,f_domain_id,f_snap_target,f_jobid,f_request_id,f_pluginname,f_sizetransferred,f_is_snap,f_node_id,f_workflow_id,f_action_name,f_agent_id,f_instancename,f_session,f_totalobjdedup,f_changedbytes,f_sizeboffset,f_dedupredtn,f_statuscodesummary,f_workflow_jobid,f_snap_policy,f_size_copies,f_sizescanned,f_sub_id,f_archive_flag,f_nfilesnot,f_media_wait,f_snap_creation,f_effective_path) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42,$43,$44,$45,$46,$47,$48,$49,$50,$51,$52,$53,$54,$55,$56,$57,$58,$59,$60,$61,$62,$63,$64,$65,$66,$67,$68,$69,$70,$71,$72,$73,$74,$75,$76,$77,$78) 2024-02-19 15:21:54.851 +08 [10928] DEBUG: bind to 2024-02-19 15:21:54.852 +08 [10928] DEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGRESS, xid/subid/cid: 0/1/0 Regards, Venkat Internal Use - Confidential From: Greg Sabino Mullane Sent: Saturday, March 16, 2024 12:07 AM To: Bandi, Venkataramana - Dell Team Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team ; Alampalli, Kishore Subject: Re: Query on Postgres SQL transaction [EXTERNAL EMAIL] That's a very vague question, but you can trace exactly what is happening by issuing SET log_statement = 'all'; Ideally at the session level by your application, but can also set it at the database and user level. If all else fails, set it globally (i.e. postgresql.conf). Turn it off again as soon as possible, it will make your logs extremely verbose. But you can track exactly what your application is doing. Cheers, Greg
Re: Query on Postgres SQL transaction
That's a very vague question, but you can trace exactly what is happening by issuing SET log_statement = 'all'; Ideally at the session level by your application, but can also set it at the database and user level. If all else fails, set it globally (i.e. postgresql.conf). Turn it off again as soon as possible, it will make your logs extremely verbose. But you can track exactly what your application is doing. Cheers, Greg
Re: Query on Postgres SQL transaction
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.kla...@aklaver.com
Query on Postgres SQL transaction
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. 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
