N\u00eb komunitet, njer\u00ebzit kan\u00eb pyetur p\u00ebr mb\u00ebshtetje p\u00ebr deklaratat e p\u00ebrgatitura.<\/a><\/noindex>Tani tani mund t\u00eb krijoni nj\u00eb prepared statement n\u00eb dy m\u00ebnyra. S\u00eb pari, mund t\u00eb ekzekutoni komand\u00ebn SQL, q\u00eb \u00ebsht\u00eb \"prepared\". P\u00ebr t\u00eb kuptuar k\u00ebt\u00eb komand\u00eb SQL, duhet t\u00eb m\u00ebsojm\u00eb t\u00eb kuptojm\u00eb SQL nga ana e Bouncer. Do t\u00eb ishte nj\u00eb overkill, sepse na nevojitet plot\u00ebsisht nj\u00eb parser. Nuk mund t\u00eb analizojm\u00eb \u00e7do komand\u00eb SQL. <\/p>\n<\/p>\n
Por ka nj\u00eb prepared statement n\u00eb nivelin e protokollit t\u00eb mesazheve n\u00eb proto3. Dhe kjo \u00ebsht\u00eb ajo vend ku informacioni p\u00ebr krijimin e prepared statement vjen n\u00eb nj\u00eb form\u00eb t\u00eb strukturuar. Ne mund ta mb\u00ebshtesim kuptimin se n\u00eb nj\u00eb lidhje serveri klienti k\u00ebrkoi t\u00eb krijoj\u00eb prepared statements. Dhe edhe n\u00ebse transaksioni p\u00ebrfundoi, na duhet ende t\u00eb mbajm\u00eb lidhshm\u00ebrin\u00eb midis serverit dhe klientit. <\/p>\n
<\/p>\n
Por k\u00ebtu ndodhet nj\u00eb mosmarr\u00ebveshje n\u00eb dialog, sepse dikush po flet p\u00ebr nevoj\u00ebn p\u00ebr t\u00eb kuptuar se cili sakt\u00ebsisht prepared statements ka krijuar klienti dhe p\u00ebr t\u00eb ndar\u00eb lidhjen e serverit midis t\u00eb gjitha kli\u00ebnteve q\u00eb krijuan k\u00ebt\u00eb lidhje serveri, pra ata q\u00eb krijuan nj\u00eb prepared statement t\u00eb till\u00eb. <\/p>\n
<\/p>\n
Andres Freund tha se n\u00ebse ju vjen nj\u00eb klient q\u00eb tashm\u00eb ka krijuar nj\u00eb prepared statement n\u00eb nj\u00eb lidhje tjet\u00ebr serveri, at\u00ebher\u00eb krijoni at\u00eb p\u00ebr t\u00eb. Por duket se \u00ebsht\u00eb pak e gabuar t\u00eb ekzekutoni k\u00ebrkesat n\u00eb baz\u00eb n\u00eb vend t\u00eb klientit, por nga k\u00ebndv\u00ebshtrimi i zhvilluesit q\u00eb shkruan protokollin e nd\u00ebrveprimit me baz\u00ebn, do t\u00eb ishte e p\u00ebrshtatshme, n\u00ebse thjesht do t'i jepnin nj\u00eb lidhje rrjeti, n\u00eb t\u00eb cil\u00ebn ka nj\u00eb k\u00ebrkes\u00eb t\u00eb till\u00eb t\u00eb p\u00ebrgatitur. <\/p>\n
<\/p>\n
<\/p>\n
Dhe nj\u00eb ve\u00e7ori tjet\u00ebr q\u00eb duhet t\u00eb implementojm\u00eb. Tani kemi monitorim, t\u00eb p\u00ebrputhsh\u00ebm me PgBouncer. Mund t\u00eb kthejm\u00eb koh\u00ebn mesatare t\u00eb ekzekutimit t\u00eb k\u00ebrkes\u00ebs. Por koha mesatare \u00ebsht\u00eb temperatura mesatare n\u00eb spital: dikush \u00ebsht\u00eb i ftoht\u00eb, ndokush \u00ebsht\u00eb i ngroht\u00eb - n\u00eb mesatare t\u00eb gjith\u00eb jan\u00eb t\u00eb sh\u00ebndetsh\u00ebm. Kjo nuk \u00ebsht\u00eb e v\u00ebrtet\u00eb. <\/p>\n
<\/p>\n
Na duhet t\u00eb realizojm\u00eb mb\u00ebshtetje p\u00ebr percentiles q\u00eb do t\u00eb tregonin se ka k\u00ebrkesa t\u00eb ngadalta q\u00eb konsumojn\u00eb burime dhe do ta b\u00ebnin monitorimin m\u00eb t\u00eb pranuesh\u00ebm. <\/p>\n
<\/p>\n
<\/p>\n
M\u00eb e r\u00ebnd\u00ebsishmja \u2013 dua versionin 1.0 (Versioni 1.1 tashm\u00eb ka dal\u00eb). \u00c7\u00ebshtja \u00ebsht\u00eb se tani Odyssey ndodhet n\u00eb versionin 1.0rc, pra release candidate. Dhe t\u00eb gjith\u00eb problemet q\u00eb p\u00ebrmenda ishin zgjidhur pik\u00ebrisht me at\u00eb version, p\u00ebrve\u00e7 memory leak. <\/p>\n
<\/p>\n
\u00c7far\u00eb do t\u00eb thot\u00eb p\u00ebr ne versioni 1.0? Ne po nxjerrim Odyssey n\u00eb bazat tona. Ai tashm\u00eb funksionon n\u00eb bazat tona, por kur t\u00eb arrij\u00eb n\u00eb pik\u00ebn e 1,000,000 k\u00ebrkesave n\u00eb sekond\u00eb, mund t\u00eb themi se kjo \u00ebsht\u00eb versioni i l\u00ebshuar dhe mund t\u00eb quhet 1.0. <\/p>\n
<\/p>\n
N\u00eb komunitet disa njer\u00ebz k\u00ebrkuan q\u00eb n\u00eb versionin 1.0 t\u00eb ishin gjithashtu pauza dhe SCRAM. Por kjo do t\u00eb thot\u00eb se do t\u00eb na duhet t\u00eb nxjerrim n\u00eb prodhim versionin e ardhsh\u00ebm, sepse as SCRAM dhe as pauza nuk jan\u00eb fqinj n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb. Megjithat\u00eb, shum\u00eb p\u00ebr s\u00eb shumti, ky problem do t\u00eb zgjidhet mjaft shpejt. <\/p>\n
<\/p>\n
<\/p>\n
Po pres k\u00ebrkesat tuaja. Dhe do t\u00eb doja gjithashtu t\u00eb d\u00ebgjoja se cilat probleme keni me Bouncer. Le t\u00eb diskutojm\u00eb p\u00ebr to. Ndoshta mund t\u00eb realizojm\u00eb disa funksione q\u00eb ju nevojiten. <\/p>\n
<\/p>\n
Me k\u00ebt\u00eb p\u00ebrfundoj pjes\u00ebn time, do doja t\u00eb d\u00ebgjoja ju. Faleminderit!<\/p>\n
<\/p>\n
Pyetje<\/p>\n
<\/p>\n
N\u00ebse vendos application_name tim, a do t\u00eb kaloj\u00eb si\u00e7 duhet, p\u00ebrfshir\u00eb n\u00eb pool-in e transaksioneve n\u00eb Odyssey?<\/em><\/p>\n<\/p>\n
N\u00eb Odyssey apo n\u00eb Bouncer?<\/p>\n
<\/p>\n
N\u00eb Odyssey. N\u00eb Bouncer kalon.<\/em> <\/p>\n<\/p>\n
Ne do t\u00eb b\u00ebjm\u00eb set-in. <\/p>\n
<\/p>\n
Dhe n\u00ebse lidhja ime e v\u00ebrtet\u00eb do t\u00eb kaloj\u00eb n\u00eb lidhje t\u00eb tjera, a do t\u00eb transferohet?<\/em><\/p>\n<\/p>\n
Ne do t\u00eb b\u00ebjm\u00eb nj\u00eb set t\u00eb t\u00eb gjitha parametrave t\u00eb renditur n\u00eb list\u00eb. Nuk mund t\u00eb them n\u00ebse n\u00eb k\u00ebt\u00eb list\u00eb ka application_name. M\u00eb duket se e kam par\u00eb atje. Ne do t\u00eb vendosim t\u00eb nj\u00ebjt\u00ebt parametra. Me nj\u00eb k\u00ebrkes\u00eb atje set do t\u00eb b\u00ebj\u00eb gjith\u00e7ka q\u00eb \u00ebsht\u00eb vendosur nga klienti gjat\u00eb fillimit. <\/p>\n
<\/p>\n
Faleminderit, Andrei, p\u00ebr raportin! Raport i mir\u00eb! G\u00ebzohem q\u00eb Odyssey po zhvillohet gjithnj\u00eb e m\u00eb shpejt \u00e7do minut\u00eb. Uroj q\u00eb t\u00eb vazhdoni k\u00ebshtu. Ne tashm\u00eb ju kemi k\u00ebrkuar t\u00eb keni lidhje multi data-source, n\u00eb m\u00ebnyr\u00eb q\u00eb Odyssey t\u00eb mund t\u00eb lidhet nj\u00ebkoh\u00ebsisht n\u00eb baza t\u00eb ndryshme t\u00eb dh\u00ebnash, dmth. master slave, dhe pastaj automatikisht pas nj\u00eb faillover t\u00eb lidhet me nj\u00eb master t\u00eb ri.<\/em> <\/p>\n<\/p>\n
Po, m\u00eb duket se e mbaj mend k\u00ebt\u00eb diskutim. Aktualisht ka disa storage. Por nuk ka kalim mes tyre. Ne duhet t\u00eb shqyrtojm\u00eb serverin n\u00eb an\u00ebn ton\u00eb, q\u00eb ai t\u00eb jet\u00eb ende n\u00eb jet\u00eb dhe t\u00eb kuptojm\u00eb se ka ndodhur nj\u00eb faillover, kush do ta th\u00ebrras\u00eb pg_recovery. Kam nj\u00eb m\u00ebnyr\u00eb standarde p\u00ebr t\u00eb kuptuar q\u00eb nuk jemi n\u00eb master. Dhe ne duhet ta kuptojm\u00eb ndonj\u00ebher\u00eb nga gabimet ose si? Pra, ideja \u00ebsht\u00eb interesante, ajo \u00ebsht\u00eb duke u diskutuar. Shkruani m\u00eb shum\u00eb komente. N\u00ebse keni duar t\u00eb pun\u00ebs q\u00eb din\u00eb C, at\u00ebher\u00eb \u00ebsht\u00eb fantastike. <\/p>\n
<\/p>\n
Ne pyetje p\u00ebr skalimin me replikat na intereson gjithashtu, sepse d\u00ebshirojm\u00eb ta b\u00ebjm\u00eb pranimin e klastereve t\u00eb replikuar sa m\u00eb t\u00eb leht\u00eb p\u00ebr zhvilluesit e aplikacioneve. Por k\u00ebtu do t\u00eb donim m\u00eb shum\u00eb komente, dometh\u00ebn\u00eb si t\u00eb b\u00ebjm\u00eb sakt\u00ebsisht, si t\u00eb b\u00ebjm\u00eb mir\u00eb. <\/p>\n
<\/p>\n
P\u00ebrs\u00ebri, kjo \u00ebsht\u00eb nj\u00eb pyetje p\u00ebr replikat. Pra, keni nj\u00eb master dhe disa replika. Dhe \u00ebsht\u00eb e qart\u00eb se n\u00eb nj\u00eb replik\u00eb vini m\u00eb rrall\u00eb se n\u00eb master p\u00ebr lidhjet, sepse ato mund t\u00eb ken\u00eb dallime. Ju keni th\u00ebn\u00eb se dallimi n\u00eb t\u00eb dh\u00ebna mund t\u00eb jet\u00eb i till\u00eb, sa nuk do t\u00eb plot\u00ebsoj\u00eb biznesin tuaj dhe nuk do t\u00eb shkoni atje derisa t\u00eb ri-replikohet. N\u00ebse pas nj\u00eb kohe t\u00eb gjat\u00eb, filloni t\u00eb shkoni atje, t\u00eb dh\u00ebnat q\u00eb ju nevojiten nuk do t\u00eb jen\u00eb menj\u00ebher\u00eb t\u00eb disponueshme. Pra, n\u00ebse vazhdimisht shkojm\u00eb n\u00eb master, aty cache \u00ebsht\u00eb ngrohur, nd\u00ebrsa n\u00eb replik\u00eb cache \u00ebsht\u00eb pak prapa.<\/em> <\/p>\n<\/p>\n
Po, \u00ebsht\u00eb e v\u00ebrtet\u00eb. N\u00eb pcache nuk do t\u00eb ket\u00eb blloqe t\u00eb dh\u00ebnash q\u00eb ju d\u00ebshironi, n\u00eb real cache nuk do t\u00eb ket\u00eb informacion rreth tabelave q\u00eb ju d\u00ebshironi, n\u00eb planet nuk do t\u00eb ket\u00eb k\u00ebrkesa t\u00eb parseruara, n\u00eb p\u00ebrgjith\u00ebsi nuk do t\u00eb ket\u00eb asgj\u00eb. <\/p>\n
<\/p>\n
Dhe kur keni nj\u00eb klaster dhe shtoni nj\u00eb replik\u00eb t\u00eb re, p\u00ebrderisa ajo starton, gjith\u00e7ka \u00ebsht\u00eb keq, dometh\u00ebn\u00eb ajo po ngre cache-in e saj.<\/em> <\/p>\n<\/p>\n
E kuptova iden\u00eb. Qasja e duhur do t\u00eb ishte t\u00eb filloni nj\u00eb p\u00ebrqindje t\u00eb vog\u00ebl t\u00eb k\u00ebrkesave fillimisht n\u00eb replik\u00eb, t\u00eb cilat do t\u00eb ngrohin cache-in. Thjesht, kemi nj\u00eb kusht q\u00eb duhet t\u00eb jemi m\u00eb shum\u00eb se 10 sekonda prapa masterit. Dhe ky kusht t\u00eb aktivizohet jo me nj\u00eb val\u00eb, por gradualisht p\u00ebr disa klient\u00eb. <\/p>\n
<\/p>\n
Po, rritni pesh\u00ebn.<\/em><\/p>\n<\/p>\n
Kjo \u00ebsht\u00eb nj\u00eb ide e mir\u00eb. Por fillimisht duhet t\u00eb implementojm\u00eb k\u00ebt\u00eb \u00e7aktivizim. Fillimisht duhet t\u00eb fikemi, pastaj do t\u00eb mendojm\u00eb se si t\u00eb ndizemi. Kjo \u00ebsht\u00eb nj\u00eb karakteristik\u00eb e shk\u00eblqyer p\u00ebr t\u00eb u ngjitur gradualisht.<\/p>\n
<\/p>\n
N\u00eb nginx ekziston nj\u00eb opsion t\u00eb till\u00eb fillimisht ngadal\u00eb nis<\/code> n\u00eb klasterin p\u00ebr serverin. Dhe ai gradualisht ndihmon n\u00eb rritjen e ngarkes\u00ebs.<\/em> <\/p>\n<\/p>\n
Po, nj\u00eb ide e shk\u00eblqyer, do ta provojm\u00eb kur t\u00eb arrijm\u00eb aty.<\/p>\n
Burimi: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"\u0412 \u0434\u043e\u043a\u043b\u0430\u0434\u0435 \u0410\u043d\u0434\u0440\u0435\u0439 \u0411\u043e\u0440\u043e\u0434\u0438\u043d \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0435\u0442, \u043a\u0430\u043a \u043e\u043d\u0438 \u0443\u0447\u043b\u0438 \u043e\u043f\u044b\u0442 \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f PgBouncer \u043f\u0440\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438 \u043f\u0443\u043b\u0435\u0440\u0430 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0439 Odyssey, \u043a\u0430\u043a \u0432\u044b\u043a\u0430\u0442\u044b\u0432\u0430\u043b\u0438 \u0435\u0433\u043e \u0432 production. \u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u043e\u0431\u0441\u0443\u0434\u0438\u043c \u043a\u0430\u043a\u0438\u0435 \u0444\u0443\u043d\u043a\u0446\u0438\u0438 \u043f\u0443\u043b\u0435\u0440\u0430 \u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0431\u044b \u0432\u0438\u0434\u0435\u0442\u044c \u0432 \u043d\u043e\u0432\u044b\u0445 \u0432\u0435\u0440\u0441\u0438\u044f\u0445: \u043d\u0430\u043c \u0432\u0430\u0436\u043d\u043e \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u0437\u0430\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0441\u0432\u043e\u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043d\u043e\u0441\u0442\u0438, \u043d\u043e \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u0442\u044c \u0441\u043e\u043e\u0431\u0449\u0435\u0441\u0442\u0432\u043e \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u041e\u0434\u0438\u0441\u0441\u0435\u044f. \u0412\u0438\u0434\u0435\u043e: \u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0410\u043d\u0434\u0440\u0435\u0439. \u0412 \u042f\u043d\u0434\u0435\u043a\u0441\u0435 \u044f \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":96516,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-96515","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t
![\"Odyssey](\"\/wp-content\/uploads\/2020\/10\/6c445191705a4c96939cd094bc457a53.jpg\")
<\/p>\n