Re: Query on Postgres SQL transaction
От | Adrian Klaver |
---|---|
Тема | Re: Query on Postgres SQL transaction |
Дата | |
Msg-id | 1df224d9-6488-4dd0-9152-d38c6468756a@aklaver.com обсуждение исходный текст |
Ответ на | RE: Query on Postgres SQL transaction ("Bandi, Venkataramana - Dell Team" <Venkataramana.Bandi@dellteam.com>) |
Список | pgsql-general |
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 frameworkto persist the data into Postgres SQL DB but for one of the request, it is also similar request like other requestsand there are no differences b/w these requests in terms of different OS, different network etc. but data is notpersisting 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 transactionand 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 xxxxxxx (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 <unnamed> to <unnamed> > 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 <adrian.klaver@aklaver.com> > Sent: Wednesday, March 27, 2024 9:32 PM > To: Bandi, Venkataramana - Dell Team <Venkataramana.Bandi@dellteam.com>; Greg Sabino Mullane <htamfids@gmail.com> > Cc: pgsql-general@lists.postgresql.org; Kishore, Nanda - Dell Team <Nanda.Kishore@Dellteam.com>; Alampalli, Kishore <Kishoreravishankar.Alampalli@dellteam.com> > 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 orno 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.klaver@aklaver.com > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления:
Следующее
От: Alexander FarberДата:
Сообщение: Re: Please recommend postgresql.conf improvements for osm2pgsql loading Europe