{"id":184329,"date":"2026-11-20T03:36:27","date_gmt":"2026-11-20T01:36:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/reliz-subd-postgresql-19"},"modified":"2026-11-20T03:36:30","modified_gmt":"2026-11-20T01:36:30","slug":"postgresql-19-released","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/news\/postgresql-19-released","title":{"rendered":"Lansarea SGBD PostgreSQL 19","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Dup\u0103 un an de dezvoltare, a fost lansat\u0103 noua ramur\u0103 stabil\u0103 a SGBD-ului PostgreSQL 19. Actualiz\u0103rile pentru noua ramur\u0103 vor ap\u0103rea timp de cinci ani, p\u00e2n\u0103 \u00een noiembrie 2031. Suportul pentru PostgreSQL 14.x, cea mai veche dintre ramurile suportate, se \u00eencheie \u00een aceast\u0103 lun\u0103. Lansarea a fost publicat\u0103 cu aproape dou\u0103 luni mai t\u00e2rziu dec\u00e2t data ini\u021bial planificat\u0103 din cauza unui flux nespecific trecutelor versiuni de raportare a erorilor, identificate prin analiza codului cu ajutorul instrumentelor AI.       <\/p>\n<p>Nout\u0103\u021bi principale:     <\/p>\n<ul>\n<li class=\"l\"> A fost \u00eembun\u0103t\u0103\u021bit\u0103 implementarea subsistemului de intrare\/ie\u0219ire asincron\u0103, permi\u021b\u00e2nd cre\u0219terea capacit\u0103\u021bii de intrare\/ie\u0219ire \u0219i eliminarea \u00eent\u00e2rzierilor. \u00cen implementarea universal\u0103 AIO (io_method=worker) a ap\u0103rut op\u021biunea de a cre\u0219te sau reduce automat num\u0103rul proceselor de manipulare a intr\u0103rii\/ie\u0219irii, \u00een func\u021bie de sarcin\u0103. Pentru determinarea num\u0103rului minim \u0219i maxim de procese-de-\u021binere, precum \u0219i a timeout-ului de inactivitate \u00eenainte de \u00eenchidere \u0219i a \u00eent\u00e2rzierii \u00eenainte de lansarea proceselor, au fost propuse parametrii io_min_workers, io_max_workers, io_worker_idle_timeout \u0219i io_worker_launch_interval.\n<p>\u00cen plus, planificatorul de citire anticipat\u0103 utilizat \u00een AIO este optimizat pentru a \u00eembun\u0103t\u0103\u021bi performan\u021ba interog\u0103rilor care necesit\u0103 \u00eenc\u0103rcarea unui volum mare de date de pe disc. Optimizarea este realizat\u0103 prin determinarea adaptiv\u0103 a num\u0103rului admis de opera\u021biuni de citire anticipat\u0103, \u00een func\u021bie de natura \u0219i dimensiunea interog\u0103rii (de exemplu, pentru opera\u021biunile de scanare a tabelelor \u0219i indicilor mari, acum se pre\u00eencarc\u0103 de pe disc mai multe date). Pentru analizarea execu\u021biei opera\u021biunilor de intrare\/ie\u0219ire \u00een mod asincron, comenzii \u201eEXPLAIN ANALYZE\u201d i s-a ad\u0103ugat op\u021biunea \u201eIO\u201d.      <\/p>\n<li class=\"l\"> Au fost ad\u0103ugate extensiile pg_plan_advice \u0219i pg_stash_advice pentru a transmite planificatorului de interog\u0103ri parametrii de sugestie pe un mini-limbaj \u201eplan advice\u201d, permi\u021b\u00e2nd influen\u021barea alegerii planurilor de execu\u021bie, fixarea planurilor alese \u0219i experimentarea cu diferite planuri. Pentru a ob\u021bine lista parametrilor ale\u0219i de planificator \u00een timpul execu\u021biei interog\u0103rii, comenzii EXPLAIN i s-a ad\u0103ugat op\u021biunea \u201ePLAN_ADVICE\u201d, iar pentru a seta propriile parametrii \u00eenainte de a executa interogarea, se poate folosi expresia \u201eSET pg_plan_advice.advice = 'string cu lista de parametrii'\u201d. Extensia pg_stash_advice completeaz\u0103 pg_plan_advice cu func\u021bionalit\u0103\u021bi pentru a lega parametrii de identificatorii interog\u0103rilor, astfel \u00eenc\u00e2t s\u0103 nu fie necesar s\u0103 fie ad\u0103uga\u021bi \u00eenainte de fiecare interogare. EXPLAIN (COSTS OFF, PLAN_ADVICE) SELECT * FROM join_fact f JOIN join_dim d ON f.dim_id = d.id; ... Plan de Sugestie Generat: JOIN_ORDER(f d) HASH_JOIN(d) SEQ_SCAN(f d) NO_GATHER(f d) SET pg_plan_advice.advice = 'JOIN_ORDER(f d) NO_GATHER(f d)';\n<li class=\"l\"> \u00cen procesul de pornire automat\u0103 a cur\u0103\u021b\u0103rii (autovacuum) a fost ad\u0103ugat\u0103 capacitatea de utilizare paralel\u0103 a mai multor gestionari la executarea cur\u0103\u021b\u0103rii indexurilor. Num\u0103rul de gestionari este configurat prin op\u021biunea autovacuum_max_parallel_workers. De asemenea, au fost ad\u0103ugate noi op\u021biuni autovacuum_vacuum_score_weight, autovacuum_vacuum_insert_score_weight \u0219i autovacuum_analyze_score_weight pentru a determina prioritatea cur\u0103\u021b\u0103rii tabelelor.\n<li class=\"l\"> A fost implementat\u0103 o nou\u0103 strategie de cur\u0103\u021bare, care permite reducerea volumului de munc\u0103 \u00een viitor, datorit\u0103 actualiz\u0103rii h\u0103r\u021bii de vizibilitate a paginilor \u00een timpul scan\u0103rii tabelelor la executarea interog\u0103rilor SELECT, f\u0103r\u0103 a a\u0219tepta lansarea comenzii VACUUM.\n<li class=\"l\"> A fost ad\u0103ugat\u0103 o nou\u0103 comand\u0103 SQL \u201eREPACK\u201d pentru a reconstrui tabelele cu cheltuieli reduse. Comanda REPACK rescrie complet tot con\u021binutul tabelei \u00eentr-un nou fi\u0219ier pe disc, ceea ce permite sistemului de operare s\u0103 recupereze spa\u021biul pe disc ocupat de blocurile neutilizate. Spre deosebire de comanda \u201eVACUUM FULL\u201d, care impune o blocare strict\u0103 \u00een timpul rescrierii, comanda REPACK are op\u021biunea \u201eCONCURRENTLY\u201d, care permite utilizarea tabelei de c\u0103tre alte tranzac\u021bii \u00een timpul repack-ing-ului. Spre deosebire de extensia pg_repack, REPACK este semnificativ mai rapid, deoarece nu ata\u0219eaz\u0103 triggeri suplimentari la tabel, dar nu suport\u0103 procesarea complet\u0103 a tabelelor sec\u021bionate.\n<li class=\"l\"> Performan\u021ba opera\u021biei INSERT a fost crescut\u0103 de p\u00e2n\u0103 la dou\u0103 ori pentru tabele \u00een care se verific\u0103 \u00eenregistr\u0103rile pe baza cheilor externe (Foreign Key). Accelerarea a fost ob\u021binut\u0103 prin utilizarea indexului pentru verificarea cheilor externe, ceea ce a permis evitarea execu\u021biei unei interog\u0103ri interne consumatoare de resurse asupra tabelei.\n<li class=\"l\"> Planificatorul de interog\u0103ri are acum capacitatea de a recunoa\u0219te opera\u021biile Anti-Join (identificarea r\u00e2ndurilor din prima tabel\u0103 pentru care nu exist\u0103 coresponden\u021be \u00een a doua tabel\u0103) \u00een interog\u0103rile complexe cu \u201eLEFT JOIN\u201d \u0219i \u00een interog\u0103rile cu expresiile \u201eNOT IN\u201d pentru a utiliza optimiz\u0103ri specifice. Aplicarea sort\u0103rii incrementale a fost extins\u0103. A fost ad\u0103ugat\u0103 optimizarea \u201eeager aggregation\u201d, care mut\u0103 opera\u021biile de agregare \u00eentr-o etap\u0103 anterioar\u0103 fuziunii tabelelor pentru a reduce num\u0103rul de r\u00e2nduri procesate \u00een timpul fuziunii. Execu\u021bia paralel\u0103 a opera\u021biunilor de scanare secven\u021bial\u0103 (parallel seq scan) a fost accelerat\u0103. Au fost minimizate construc\u021biile \u201eIS DISTINCT FROM\u201d \u0219i \u201eIS NOT DISTINCT FROM\u201d la expresii cu operatorii \u201e\u201d \u0219i \u201e=\u201d, dac\u0103 ambele operande nu pot lua valoarea NULL.\n<li class=\"l\"> Eficien\u021ba livr\u0103rii notific\u0103rilor prin intermediul comenzii NOTIFY \u00een configura\u021bii cu mai multe canale de notificare a fost \u00eembun\u0103t\u0103\u021bit\u0103. \u00cen memoria partajat\u0103 acum este p\u0103strat\u0103 o hart\u0103 a canalelor, permi\u021b\u00e2nd adresarea direct\u0103 doar c\u0103tre backend-urile care sunt abonate la canalul specificat.\n<li class=\"l\"> \u00cen comanda \u201eINSERT\u201d a fost ad\u0103ugat\u0103 suport pentru expresia ON CONFLICT DO SELECT \u2026 RETURNING, care returneaz\u0103 \u00eenregistr\u0103rile \u00een cazul imposibilit\u0103\u021bii de a le ad\u0103uga prin \u201eINSERT\u201d, pe l\u00e2ng\u0103 expresiile \u201eON CONFLICT DO NOTHING\/UPDATE\u201d, care ignor\u0103 \u00een t\u0103cere conflictele la inserare sau efectueaz\u0103 actualiz\u0103ri \u00een loc de inser\u021bii.\n<li class=\"l\"> Comenzii COPY i-a fost ad\u0103ugat suportul pentru exportul datelor \u00een format JSON.\n<li class=\"l\"> \u00cen SQL\/JSON au fost ad\u0103ugate metode pentru procesarea stringurilor lower(), upper(), replace(), split_part() \u0219i btrim().\n<li class=\"l\"> Func\u021biile fereastr\u0103 lead(), lag(), first_value(), last_value() \u0219i nth_value() au fost extinse cu suport pentru expresia \u201eIGNORE NULLS\u201d pentru a omite valorile NULL.\n<li class=\"l\"> A fost ad\u0103ugat\u0103 comanda \u201eWAIT FOR LSN\u201d, care, \u00een cazul replic\u0103rii asincrone, permite suspendarea unei interog\u0103ri SELECT pe serverul replicat p\u00e2n\u0103 c\u00e2nd modific\u0103rile de pe serverul principal sunt aplicate, pentru a preveni afi\u0219area datelor \u00eenvechite. <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/ro\/server\/dts-los-angeles\/\"   title=\"server\" data-wpil-keyword-link=\"linked\">server<\/a>, corespunz\u0103toare unei anumite pozi\u021bii LSN (Log Sequence Number) \u00een jurnalul WAL.\n<li class=\"l\"> Func\u021bia random() a fost extins\u0103 pentru a suporta tipurile date \u0219i timestamp pentru generarea de date \u0219i timp aleatorii \u00eentr-un interval specificat.\n<li class=\"l\"> A fost ad\u0103ugat\u0103 func\u021bionalitatea de a crea func\u021bii \u00een limbajul PL\/Python pentru declan\u0219atoare de evenimente (event trigger).\n<li class=\"l\"> \u00cencreased support for incoming network connections. <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/ro\/server\/\"   title=\"serverul\" data-wpil-keyword-link=\"linked\">serverul<\/a> A fost ad\u0103ugat\u0103 suportul pentru extensia TLS SNI (Server Name Indication) pentru utilizarea certificatelor TLS legate de numele gazdelor la care se conecteaz\u0103 clientul la stabilirea unei conexiuni criptate printr-o singur\u0103 adres\u0103 IP.\n<li class=\"l\"> \u00cen fi\u0219ierul de configurare postgresql.conf a fost ad\u0103ugat parametrul password_expiration_warning_threshold, prin care se poate configura afi\u0219area unui avertisment cu privire la expirarea iminent\u0103 a parolei.\n<li class=\"l\"> Afi\u0219area avertismentelor \u00een modul implicit a fost activat\u0103 la utilizarea algoritmului MD5 pentru autentificare, care a fost declarat \u00eenvechit. Pentru dezactivarea acestor avertiz\u0103ri, a fost ad\u0103ugat parametrul md5_password_warnings.\n<li class=\"l\"> Au fost ad\u0103ugate vizualiz\u0103ri: \u201epg_stat_lock\u201d pentru vizualizarea statisticilor acumulate despre blocaje \u00een func\u021bie de tipurile de blocaje; \u201epg_stat_recovery\u201d pentru ob\u021binerea informa\u021biilor despre starea opera\u021biunilor de recuperare; \u201epg_stat_autovacuum_scores\u201d pentru determinarea priorit\u0103\u021bii prelucr\u0103rii tabelelor \u00een autovacuum. \u00cen multe vizualiz\u0103ri sistemice a fost ad\u0103ugat un coloan\u0103 \u201estats_reset\u201d, care reflect\u0103 ultima dat\u0103 de resetare a contorului. \u00cen vizualiz\u0103rile \u201epg_stat_progress_vacuum\u201d \u0219i \u201epg_stat_progress_analyze\u201d a fost ad\u0103ugat\u0103 coloana \u201estarted_by\u201d, care arat\u0103 ini\u021biatorul opera\u021biei. \u00cen vizualizarea pg_stat_progress_vacuum a fost ad\u0103ugat\u0103 coloana \u201emode\u201d, care reflect\u0103 modul aplicat de cur\u0103\u021bare.\n<li class=\"l\"> A fost ad\u0103ugat\u0103 posibilitatea de a specifica nivelurile minime de informare a jurnalele (log_min_messages) \u00een func\u021bie de tipurile de procese.\n<li class=\"l\"> \u00cen statistica afi\u0219at\u0103 dup\u0103 opera\u021biile VACUUM \u0219i ANALYZE, precum \u0219i \u00een vizualizarea &#171;pg_stat_wal&#187;, au fost ad\u0103ugate informa\u021bii despre dimensiunea paginilor complete scrise \u00een jurnalul WAL, ceea ce faciliteaz\u0103 analiza cauzelor cre\u0219terii excesive a jurnalului WAL (se poate determina dac\u0103 aceast\u0103 cre\u0219tere este legat\u0103 de utilizarea parametrului full_page_writes).\n<li class=\"l\"> Mecanismul de replicare logic\u0103 a fost extins pentru a sprijini replicarea valorilor secven\u021belor (SEQUENCE), care pot fi publicate prin comanda &#171;CREATE PUBLICATION&#187; folosind expresia &#171;FOR ALL SEQUENCES&#187;.\n<li class=\"l\"> A fost ad\u0103ugat sintaxa &#171;CREATE PUBLICATION &#8230; EXCEPT&#187; pentru replicarea tuturor tabelelor, cu excep\u021bia celor specificate explicit.\n<li class=\"l\"> A fost ad\u0103ugat\u0103 expresia &#171;CREATE SUBSCRIPTION &#8230; SERVER&#187;, care permite crearea de subscrip\u021bii pentru replicarea logic\u0103, ob\u021bin\u00e2nd set\u0103rile de conectare de la un server extern.\n<li class=\"l\"> A fost ad\u0103ugat\u0103 posibilitatea de a activa replicarea logic\u0103 \u00een timp real f\u0103r\u0103 a reporni serverul, chiar dac\u0103 parametrul &#171;wal_level&#187; este setat pe &#171;replica&#187; \u00een loc de &#171;logical&#187;. Pentru a determina nivelul efectiv al jurnaliz\u0103rii, care nu este legat de setarea wal_level din fi\u0219ierul de configurare, a fost ad\u0103ugat parametrul &#171;effective_wal_level&#187;.\n<li class=\"l\"> \u00cen mecanismul de conectare a tabelelor externe Foreign Data Wrapper (postgres_fdw) au fost implementate posibilit\u0103\u021bi pentru transmiterea opera\u021biunilor cu array-uri pe serverul remote \u0219i a fost ad\u0103ugat\u0103 op\u021biunea import_stats pentru importul statisticilor pentru tabelele de pe un server extern atunci c\u00e2nd se execut\u0103 comanda ANALYZE pentru a \u00eembun\u0103t\u0103\u021bi eficien\u021ba planific\u0103rii locale a execu\u021biei interog\u0103rilor.\n<li class=\"l\"> Compilarea JIT este dezactivat\u0103 \u00een mod implicit, deoarece c\u00e2\u0219tigul semnificativ \u00een performan\u021b\u0103 se realizeaz\u0103 \u00een principal pentru interog\u0103rile analitice complexe, iar \u00een sarcinile obi\u0219nuite OLTP poate duce la sc\u0103deri de performan\u021b\u0103 din cauza predic\u021biilor eronate privitoare la resursele necesare pentru execu\u021bia interog\u0103rilor.\n<li class=\"l\">  Pentru a \u00eembun\u0103t\u0103\u021bi performan\u021ba comprim\u0103rii \u0219i decomprim\u0103rii tabelelor TOAST, parametrul &#171;default_toast_compression&#187; a fost setat pe &#171;lz4&#187;.\n<li class=\"l\"> Suportul pentru autentificarea utiliz\u00e2nd protocolul RADIUS a fost eliminat.\n<li class=\"l\"> \u00cen comanda &#171;vacuumdb &#8212;analyze-only&#187; analiza tabelelor sec\u021bionate este activat\u0103 implicit.<\/ul>\n<p>Din cauza problemelor identificate \u00een etapa final\u0103 de testare, unele func\u021bionalit\u0103\u021bi prezentate \u00een versiunea beta nu au fost incluse \u00een lansare, cum ar fi sintaxa &#171;GROUP BY ALL&#187;, suportul pentru formate de ie\u0219ire non-text \u00een pg_dumpall, SQL\/PGQ pentru interog\u0103ri grafice, activarea \u00een timp real a suportului pentru checksum-uri f\u0103r\u0103 repornire \u0219i reinicializare, expresia &#171;FOR PORTION OF&#187; \u00een UPDATE \u0219i DELETE, expresiile &#171;ALTER TABLE &#8230; MERGE PARTITIONS&#187; \u0219i &#171;ALTER TABLE &#8230; SPLIT PARTITIONS&#187; pentru reorganizarea tabelelor sec\u021bionate, setarea LC_COLLATE la &#171;C&#187; pentru procesul postmaster \u0219i noile func\u021bii pg_get_role_ddl(), pg_get_tablespace_ddl() \u0219i pg_get_database_ddl(). Sponsorul \u0219tirii este compania Hi-Square, dezvoltator al platformei Low Code XSQUARE pe PostgreSQL (publicitate, SRL &#171;Hi-Square&#187;, CUI 7718990614).<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=66693\">opennet.ro<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430. \u041f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0430 PostgreSQL 14.x, \u0441\u0430\u043c\u043e\u0439 \u0441\u0442\u0430\u0440\u043e\u0439 \u0438\u0437 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u043c\u044b\u0445 \u0432\u0435\u0442\u043e\u043a, \u043f\u0440\u0435\u043a\u0440\u0430\u0449\u0435\u043d\u0430 \u0432 \u044d\u0442\u043e\u043c \u043c\u0435\u0441\u044f\u0446\u0435. \u0420\u0435\u043b\u0438\u0437 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d \u043f\u043e\u0447\u0442\u0438 \u043d\u0430 \u0434\u0432\u0430 \u043c\u0435\u0441\u044f\u0446\u0430 \u043f\u043e\u0437\u0434\u043d\u0435\u0435 \u0438\u0437\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e \u043d\u0430\u043c\u0435\u0447\u0435\u043d\u043d\u043e\u0439 \u0434\u0430\u0442\u044b \u0438\u0437-\u0437\u0430 \u043d\u0435\u0441\u0432\u043e\u0439\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0448\u043b\u044b\u043c \u0432\u044b\u043f\u0443\u0441\u043a\u0430\u043c \u043f\u043e\u0442\u043e\u043a\u0430 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u043e\u0448\u0438\u0431\u043a\u0430\u0445, \u0432\u044b\u044f\u0432\u043b\u0435\u043d\u043d\u044b\u0445 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-184329","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Alexander Kovalev\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/news\/postgresql-19-released\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 \u0421\u0423\u0411\u0414 PostgreSQL 19 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/news\/postgresql-19-released\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-11-20T01:36:27+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-20T01:36:30+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Lansarea SGBD PostgreSQL 19 | ProHoster","description":"Dup\u0103 un an de dezvoltare, a fost publicat noua ramur\u0103 stabil\u0103 a SGBD-ului PostgreSQL 19. Actualiz\u0103rile pentru noua ramur\u0103 vor fi lansate pe parcursul a cinci ani, p\u00e2n\u0103 \u00een noiembrie 2031.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/news\/postgresql-19-released","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 \u0421\u0423\u0411\u0414 PostgreSQL 19 | ProHoster","og:description":"\u041f\u043e\u0441\u043b\u0435 \u0433\u043e\u0434\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u0430\u044f \u0432\u0435\u0442\u043a\u0430 \u0421\u0423\u0411\u0414 PostgreSQL 19. \u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0442\u043a\u0438 \u0431\u0443\u0434\u0443\u0442 \u0432\u044b\u0445\u043e\u0434\u0438\u0442\u044c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u044f\u0442\u0438 \u043b\u0435\u0442 \u0434\u043e \u043d\u043e\u044f\u0431\u0440\u044f 2031 \u0433\u043e\u0434\u0430.","og:url":"https:\/\/prohoster.info\/ro\/blog\/news\/postgresql-19-released","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2026-11-20T01:36:27+00:00","article:modified_time":"2026-11-20T01:36:30+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":[],"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/184329","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=184329"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/184329\/revisions"}],"predecessor-version":[{"id":184330,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/184329\/revisions\/184330"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=184329"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=184329"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=184329"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}