#postgre

[algoworks]

Most of today's web applications require a database behind it that drives data to the website and gets data from users. Let's explore the best Web Development Databases of 2022.

For more information, visit the page: https://www.algoworks.com/blog/best-database-for-web-development-in-2022/

[kaarainfosystem]

#Kaara We are Hiring for the position of "Full Stack Developer" Exp:- 3-8 Years Location:- Remote (WFH) Notice:- Max 20 days Required Skills:- - Java - Vue.js - PostgreSQL Interested Candidates Share your portfolio / CV to careers@kaaratech.com

[govindhtech]

Introducing AlloyDB AI for PostgreSQL

Not just for chatbots that respond in a human-like manner, but also for the way it can open up completely new user experiences, generative AI has captured our attention in countless ways. Additionally, these new generation AI workloads are accessible to a wider range of the developer community than traditional AI workloads, which call for additional specialized skills. The innovation in next-generation artificial intelligence applications will lie not just in the models themselves but also in their application and the data that underpins it.

At Google Cloud Next today, we introduced AlloyDB AI, an integrated set of features built into AlloyDB for PostgreSQL that will assist developers in creating scalable and effective generation AI applications using operational data. By offering built-in, end-to-end support for vector embeddings, AlloyDB AI enables developers to more quickly and effectively combine the power of large language models (LLMs) with their real-time operational data.

[itsjunetime]

new post time!

i made a post on my blog! you can read it here! it’s mostly about building my blog (with rust, axum, postgres, nginx, etc), the various issues and iterations i went through, and how i got it down from an initial ~1.2MB load (to retrieve the main page) to ~9kb. i also linked the code for my blog at the bottom of it, so hopefully that’s fun to poke thru :)

hope yall enjoy it!

[rabbiteclair]

some day I will make a class of nothing but annotations

[mourning-again-in-america]

localhost != 127.0.0.1 is the bane of my existence

[codeonedigest]

AWS EC2 VM Setup | Run Springboot Microservice and Postgres DB in EC2 Se...

 Hello friends, a new #video on #aws #cloud #ec2 #server setup #springboot #microservice setup in #ec2server #postgres setup in #ec2instance is published on #codeonedigest #youtube channel. Learn #awsec2 #postgressetup #java #programming #coding with codeonedigest.

 @java #java #awscloud @awscloud @AWSCloudIndia #Cloud #CloudComputing @YouTube #youtube  #springbootmicroservices #springbootmicroservicesproject #springbootmicroservicestutorial #springbootmicroservicesfullcourse #springbootmicroservicesexample #springbootmicroservicesarchitecture #aws #awscloud #cloud #createawsec2server #createawsec2instance #createawsec2 #awsmanagementconsole #createec2instanceinaws #createec2 #createec2instanceandconnect #createec2instanceinawslinux #awsec2 #awsec2instance #awsec2interviewquestionsandanswers #awsec2instancecreation #awsec2deploymenttutorial #installpostgresec2install #installpostgresec2linux #awsec2connect #awsec2statuschecks #awsec2project #awsec2full #awsec2createinstance #awsec2interviewquestionsandanswersforfreshers #awsec2instancedeployment #awsec2 #awsec2serialconsole #awsec2consolewindows #awsec2serverrefusedourkey #awsec2serialconsolepassword #awsec2serviceinterviewquestions #awsec2serialconsoleaccess #awsec2serialrefusedourkeyputty #awsec2serverconfiguration #awsec2serialconnect #awsec2 #awsec2instance #awsec2instancecreation #awsec2instanceconnect #awsec2instancedeployment #awsec2instancelinux #awsec2instancelaunch #awsec2instanceconnectnotworking #awsec2instanceinterviewquestions #awsec2instancecreationubuntu #awstutorial #awsec2tutorial #ec2tutorial #postgresandpgadmininstall #postgresandpgadmininstallwindows #postgresandpgadmininstallubuntu #postgresandpgadmininstallwindows11 #postgresandpgadmininstallmacos #postgresandpgadmininstallwindows10 #postgrespasswordreset #postgrestutorial #postgresdocker #postgresinstallationerror #postgres #postgresdatabase #rdbms #postgresdatabasesetup #postgresdatabaseconfiguration #database #relationaldatabase #postgresconfiguration #postgresconfigurationfile #postgresconfigurationparameters #postgresconfigfilelocation #postgresconfigurationinspringboot #postgresconfigfilewindows #postgresconfigfilemax #postgresconfigfileubuntu #postgresconfigurereplication #postgresconfigurationsettings #postgresconnectiontoserver #postgresconnectioninjava #postgresconnectioncommandline #postgresconnectioninnodejs#postgrestutorial #postgresdocker #postgresinstallationerror #postgres #postgresdatabase #rdbms #postgresdatabasesetup #postgresdatabaseconfiguration #database #relationaldatabase #postgresconfiguration #postgresconfigurationfile #postgresconfigurationparameters #postgresconfigfilelocation #postgresconfigurationinspringboot #postgresconfigfilewindows #postgresconfigfilemax #postgresconfigfileubuntu #postgresconfigurereplication #postgresconfigurationsettings #postgresconnectiontoserver #postgresconnectioninjava #postgresconnectioncommandline #postgresconnectioninnodejs

Hello Friend, Thanks for following us here. 

[stxalq]

crucially they're not an AI bot anyways. last i checked haiku bots are essentially student-showcases of "today i learned about text-vectoring in PostgreSQL" and aren't all that impressive at the end of the day

AI bots are trash, the only bot we all love here is haiku bot

[it-system-engineer]

vCenter Server Postgre Veritabanı ile İletişim Kurmak

Merhaba, bu yazımda sizlere vCenter server postgre veritabanı ile iletişim kurmak konusundan bahsedeceğim. Bu sayede eğer ortamınızda silinmiş ancak aşağıdaki gibi inaccessible olarak görünen bileşenleri temizleyebilirsiniz. Bunun için ilk olarak yapmanız gereken SSH ile vCenter sunucunuza bağlanmanız gerekmektedir. vCenter Server Appliance 6.5/6.7/7.0‘ın yerleşik vPostgres Veritabanına bağlanmak…

[chelnik]

Helping Tux out at the Ubuntu booth

[offbrandtech]

ElephantSQL - Elephants can remember, which makes them perfect for databases.

[thedbahub]

How to Convert a SQL Server Stored Procedure to PostgreSQL

Are you migrating a database from SQL Server to PostgreSQL? One key task is converting your stored procedures from T-SQL to PL/pgSQL, PostgreSQL’s procedural language. In this article, you’ll learn a step-by-step process for translating a SQL Server stored procedure to its PostgreSQL equivalent. By the end, you’ll be able to confidently port your T-SQL code to run on Postgres. Understand the…

[pgxn]

Recent PGXN Improvements

One of the perks of my new gig at Tembo is that I have more time to work on PGXN. In the last ten years I've had very little time to give, so things have stagnated. The API, for example, hasn't seen a meaningful update since 2016!

But that's all changed now, and every bit of the PGXN architecture has experienced a fair bit of TLC in the last few weeks. A quick review.

PGXN Manager

PGXN Manager provides user registration and extension release services. It maintains the root registry of the project, ensuring the consistency of download formatting and naming ($extension-$version.zip if you're wondering). Last year I added a LISTEN/NOTIFY queue for publishing new releases to Twitter and Mastodon, replacing the old Twitter posting on upload. It has worked quite well (although Twitter killed the API so we no longer post there), but has sometimes disappeared for days or weeks at a time. I've futzed with it over the past year, but last weekend I think I finally got to the bottom of the problem.

As a result, the PGXN Mastodon account should say much more up-to-date than it sometimes has. I've also added additional logging capability, because sometimes the posts fail and I need better clarity into what failed and how so it, too, can be fixed. So messaging should continue to become more reliable. Oh, and testing and unstable releases are now prominently marked as such in the posts (or will be, next time someone uploads a non-stable release).

I also did a little work on the formatting of the How To doc, upgrading to MultiMarkdown 6 and removing some post-processing that appended unwanted backslashes to the ends of code lines.

PGXN API

PGXN API (docs) has been the least loved part of the architecture, but all that changed in the last couple weeks. I finally got over my trepidation and got it working where I could hack on it again. Turns out, the pending issues and to-dos — some dating back to 2011! — weren't so difficult to take on as I had feared. In the last few weeks, API has finally come unstuck and evolved:

Switched the parsing of Markdown documents from the quite old Text::Markdown module to CommonMark, which is a thin wrapper around the well-maintained and modern cmark library. The main way in which this change will be visible is in the support for fenced code blocks. Compare the pg_later 0.0.14 README, formatted with the old parser, with pg_later 0.1.0 README, formatted with the new parser.

Updated the full text indexer to index the file identified in the META.json as the documentation for an extension even if the file name is different from the extension (issue 10), including the README.

Furthermore, if the indexer finds no documentation for the extension, either in its metadata or an appropriately-named file, it falls back on the README (issue 12).

These two fixes, the oldest and most significant of the whole system, greatly increase the accuracy of documentation search, because so many extensions have no docs other than the README. Prior to this fix, for example, a search for "later" failed to turn up pg_later, and now it's appropriately the first result.

The indexer now indexes releases marked "testing" or "unstable" in the metadata if there is no stable release (issue 2!). This makes new extensions under development easier to find on the site than previously, when only stable releases were indexed. However, once a stable release is made, no more testing or unstable releases will be indexed. I believe this is more intuitive behavior.

Also fixed some permissions issue, ensuring that source code unzipped for browsing is accessible to the app. In other words, a zip file without READ permission would trigger a not found response; the API now ensures that all files and directories are accessible to the application.

As a bonus, the API now also recognizes plain text files (.txt and .text) as documentation and indexes their contents and adds links for display on the site. Previously plain text files other than READMEs were ignored (issue 13).

I'm quite pleased with some of these fixes, and relieved to have finally cleared out the karmic overhang of the backlog. But the indexing and HTML rendering changes, in particular, are tactical: until the entire registry can be re-indexed, only new uploads will benefit from the indexing improvements. I hope to find time to work on the indexing project soon.

PGXN Site

The pgxn-site project powers the main site, pgxn.org, and has seen 7 new releases since the beginning of the year! Notable changes:

Changed the default search index from Documentation too Distributions, because most release include no docs other than a READMe, which was indexed as part of the distribution and not the extension contained in a distribution. As a result, searches return more relevant and comprehensive results. However, I say "was indexed" because, as described above, the PGXN API has since been updated to appropriately identify and index READMEs as extension documentation. So this change might get reverted at some point, but not before the entire registry can be re-indexed.

Changed the link to the How To in the footer from the somewhat opaque "Release It!" to "Release on PGXN". Should make it clearer what it is. Also, have you considered releasing your extension on PGXN? You should!

Fixed "not found" errors for links to files with uppercase letters, such as /dist/vectorize/vector-serve/README.html.

Tweaked the CSS a bit to improve list item alignment in the "Contents" of doc pages (like semver), as well as the spacing between definition lists, as in the FAQ.

Switched the parsing and formatting of the static pages (about, art, FAQ, feedback, and mirroring) from the quite ancient Text::MultiMarkdown module to MultiMarkdown 6.

Oh, and I fixed or removed a bunch of outdated links from those pages, and replaced all relevant HTTP URLs with HTTPS URLs. Then had to revert those changes from a bunch of SVG files, where xmlns="http://www.w3.org/2000/svg" is relevant but xmlns="https://www.w3.org/2000/svg" is not. 🤦🏻‍♂️

Grab Bag

I've made a number of more iterative improvements, as well, mostly to the maintainability of PGXN projects:

The GitHub repositories for all of these projects have been updated with comprehensive test and release workflows, as well as improved Perl release configuration.

The WWW::PGXN, PGXN::API::Searcher Perl modules have been updated with test and release workflows and improved Perl release configuration, as well.

The libexec configuration of the PGXN Client Homebrew formula has been fixed, allowing PGXN::Meta::Validator to install itself in the proper place to allow pgxn validate-meta to work properly on Homebrew managed-systems (like mine!)

The pgxn/pgxn-tools Docker image, which saw some fixes and improvements last month, has continued to evolve, as well. Recent improvements include support for PostgreSQL TAP tests (not to be confused with pgTAP, already supported), finer control over managing the Postgres cluster — or multiple clusters — by setting NO_CLUSTER= to prevent pg-start from creating the cluster. Both these improvements better enable multi-cluster testing.

The End

I think that about covers it. Although I'm thinking and writing quite a lot about what's next for the Postgres extension ecosystem, I expect to continue tending to the care and feeding and improvement of PGXN as well. To the future!