Хөгжүүлэлтийн явцад LLM ашиглан код шалгах үйл явц эрчимжсэнтэй холбоотойгоор PostgreSQL 19 хувилбарын нээлтийг 11 дүгээр сарын 19-нийг хүртэл хойшлуулж, олон тооны шинэ боломжуудыг дараагийн хувилбар руу шилжүүлэв
PostgreSQL Global Development Group нээлттэй эх сурвалжтай алдартай өгөгдлийн сангийн шинэ хувилбар болох PostgreSQL 19-ийг албан ёсоор гаргах хугацааг хойшлуулж, төлөвлөгдсөн 8-10 орчим чухал шинэчлэлийг хасахаар шийдвэрлэжээ. EDB компанийн дэд ерөнхийлөгч бөгөөд PostgreSQL төслийн тэргүүлэх хөгжүүлэгч Питер Айзентраутын тайлбарласнаар, энэхүү өөрчлөлт нь хөгжүүлэлтийн явцад ашигласан хиймэл оюун ухаант (LLM) код шалгах технологитой шууд холбоотой байна.
Тус технологи нь урьд өмнө нь анзаарагдалгүй өнгөрдөг байсан олон жижиг алдааг илрүүлснээр хөгжүүлэгчдэд засварлах ажлын ачааллыг нэмэгдүүлжээ. Питер Айзентраутын хэлснээр, зарим шинэ боломжууд архитектурын хувьд томоохон доголдолтой байсан нь бета шатанд бүрэн засахад хүндрэлтэй байсан тул тэдгээрийг PostgreSQL 20 хувилбар руу шилжүүлсэн байна. Үүнд SQL стандарт дахь SQL/PGQ (Property Graph Queries) дэмжлэгийг багтаасан бөгөөд уг функцийг бүрэн гүйцэд болгох шаардлагатай гэж үзжээ.
Хэдийгээр нээлтийн хугацаа хойшилсон ч PostgreSQL 19 нь REPACK CONCURRENTLY зэрэг чухал функцуудыг багтаасан найдвартай хувилбар болох төлөвтэй байна. Өмнө нь зөвхөн алдаа засварлах хувилбар гэж төлөвлөгдөж байсан PostgreSQL 20 нь одоо энэ удаагийн шинэчлэлээс үлдсэн боломжуудыг агуулах боломжтой болжээ. Хөгжүүлэгчид хиймэл оюун ухааны тусламжтай код шалгах чадвар сайжирснаар ирээдүйн хөгжүүлэлтийн мөчлөгүүд илүү үр дүнтэй болохыг онцолж байна.
Дэлгэрэнгүйг эх сурвалжаас харах
↓Эх сурвалжийг нээх ↓
The PostgreSQL Global Development Group has delayed the release of PostgreSQL 19, the latest iteration of the popular open source database, and held back an unusual number of features. Once slated for release in late September or early October, PostgreSQL 19 is now expected to be generally available around November 19. Developers have also dropped between eight and 10 significant features. Explaining the number of reverts — features whose rollouts have now been postponed to next year’s release, PostgreSQL 20 — Peter Eisentraut, veep at EDB, a PostgreSQL support and consultancy, said the reason could be at least in part attributed to the LLM code reviews used by developers. In a blog post, Eisentraut, who is a leading PostgreSQL committer, said some of the reverted features had significant architectural defects that would have been hard to fix “quickly and during beta.” However, the introduction of LLM-assisted code review also uncovered a long tail of “relatively harmless issues involving various edge cases” which, in past times, developers might not have noticed until much later, most likely issuing bug fixes in the five years following launch. “With LLM-assisted code review, these kinds of things can get found much faster, and then you’re staring at a list of forty defect reports. Even if each of them requires only a three-line fix on average, there is a fixed overhead to dealing with each of these, and then you run out of time.” When the big updates for PostgreSQL 19 were written, LLM-assisted code review was not as useful as it is now, we’re told, but in the months leading up to the launch, the AI-supported reviews became better understood and more effective. “The effective quality bar has been raised after the time the feature was written and committed. Unless the capabilities of LLM-assisted code review keep improving at the current rate, this situation should sort itself out for future development cycles,” Eisentraut said. He was also at pains to point out that the reverts were not down to “vibe coding” in development, as the technique was not available when most of the new features were written. Postgres was first proposed by Michael Stonebraker in 1986. In 1994, Andrew Yu and Jolly Chen replaced the query language POSTQUEL with SQL, and in 1995 made the database freely available and modifiable under a more permissive license, renaming it PostgreSQL. It has since become the most popular database among professional developers owing to the services the big three hyperscalers built on it as well as the range of wire-compatible distributed systems available. Among the features pulled from the PostgreSQL 19 iteration is support for SQL Property Graph Queries (SQL/PGQ), which became part of the SQL standard in 2023. The feature provides syntax for exploring relationships between nodes connected by edges. PostgreSQL’s implementation was removed over unresolved issues. At the time, PostgreSQL contributor Tom Lane warned: “At this point I’d be willing to bet dinner that if we ship it in v19 there will be post-release bug discoveries that are unfixable until v20.” Despite the delay, Eisentraut promises PostgreSQL 19 will still be “a great release,” that includes REPACK CONCURRENTLY, which avoids the table-lock VACUUM FULL operation used to reclaim disk space. “And it will be very robust, after all the additional scrutiny,” he said. The features reverted from PostgreSQL 19 will likely make it into PostgreSQL 20. Just a few months ago, developers expected PostgreSQL 20 to have no new features, just bug fixes. Now, it is likely to have the new features left over from the earlier release, Eisentraut said.®
