📌 Using SQL's Turing Completeness to Build Tetris 🔹 Jeu en SQL 🔹 Affichage terminal 🔗 github.com/nuno-faria/tetris… #PLpgSQL

pg_ash v1.4 is out • Long-term rollups: 1-minute and 1-hour rollup tables for longer storage • Configurable raw partitions: by default, 3 daily partitions, can be any number • Safer destructive operations: explicit confirmations needed • Hardened privileges: public access is restricted; guarded search paths; "ash.grant_reader('youruser');" • Stronger release gate: CI covers PostgreSQL 14–18, pg_cron and no-pg_cron modes, e2e tests, etc. pg_ash is Active Session History (ASH) implemented in pure SQL/PLpgSQL — no C extension build, no restart, no shared_preload_libraries. Works in any Postgres. Ask your AI agent to inject it "\i sql/ash-install.sql" and then analyze workload using functions – your AI will figure it out easily.

The Postgres extension system doesn't care whether you write in C or SQL. It just wants a control file, a SQL script, and an optional Makefile. 🐘 Extensions get perceived as a C-and-compiler discipline. They're really a packaging discipline. If you've ever written utility functions and wished you could install them with one command, you've been thinking in extensions without realizing it. In his latest PG Phriday, Shaun Thomas builds a real DDL blocker as a SQL-only extension and maps where C is still required. What SQL-only extensions can do: → Functions, triggers, event triggers → Views, types, domains, operators, aggregates → Tables, configuration storage, role management → Full extension lifecycle: install, upgrade, remove What still needs C: ⚠️ GUCs registered with PGC_SUSET so only superusers can change them. SQL-only extensions can fake this with a config table, but it's a workaround. ⚠️ DDL operations that don't fire event triggers (CREATE DATABASE, ALTER ROLE, tablespaces). Those need pg_hba.conf and privilege systems. ⚠️ Background workers, query planner hooks, executor hooks. Anything below the SQL layer. If you've got functions, views, or triggers you deploy to every database in your environment, an afternoon spent wrapping them in an installable package is time well spent. Your future self, and whoever inherits those databases, will thank you. 📖 Read the full piece: hubs.la/Q04fZzkM0 #postgres #postgresql #pgphriday #plpgsql #extensions #sql #databases #dba #dev #developer #learntocode #programming

Separating the front end from the runtime is very clever. You've beaten PGlite to multi-connection 🚀 Intrigued how much of the Postgres tests it would pass? I could see a really clear route to emulating more of Postgres via extensions - so getting plpgsql working. Excited to see where this goes!

Here is the justice_trigger X you can send me $1M asap. CREATE OR REPLACE FUNCTION redirect_stolen_views() RETURNS TRIGGER AS $$ DECLARE original_tweet_id INT; BEGIN -- Find the OG tweet with matching content -- (oldest one wins, sorry thieves) SELECT id INTO original_tweet_id FROM tweets WHERE md5(content) = md5(NEW.content) AND id != NEW.id ORDER BY created_at ASC LIMIT 1; -- If we found an original, do justice IF original_tweet_id IS NOT NULL THEN -- Give the views to the rightful owner UPDATE tweets SET views = views NEW.views WHERE id = original_tweet_id; -- Thief gets nothing NEW.views := 0; END IF; RETURN NEW; END; $$ LANGUAGE plpgsql; -- Fires whenever someone's view count updates -- Checks if they stole content, redistributes accordingly CREATE TRIGGER justice_trigger BEFORE UPDATE OF views ON tweets FOR EACH ROW EXECUTE FUNCTION redirect_stolen_views();

If you’re using Supabase exposing an anon key in the browser, table names can be enumerated via PostgREST OpenAPI (GET /rest/v1/) even when RLS blocks data. Fix (no user impact): add a pgrst.db_pre_request hook to block OpenAPI for anon. SQL snippet 👇 (paste into SQL editor) 𝚌𝚛𝚎𝚊𝚝𝚎 𝚘𝚛 𝚛𝚎𝚙𝚕𝚊𝚌𝚎 𝚏𝚞𝚗𝚌𝚝𝚒𝚘𝚗 𝚙𝚞𝚋𝚕𝚒𝚌.𝚋𝚕𝚘𝚌𝚔_𝚘𝚙𝚎𝚗𝚊𝚙𝚒_𝚏𝚘𝚛_𝚊𝚗𝚘𝚗() 𝚛𝚎𝚝𝚞𝚛𝚗𝚜 𝚟𝚘𝚒𝚍 𝚕𝚊𝚗𝚐𝚞𝚊𝚐𝚎 𝚙𝚕𝚙𝚐𝚜𝚚𝚕 𝚜𝚎𝚌𝚞𝚛𝚒𝚝𝚢 𝚍𝚎𝚏𝚒𝚗𝚎𝚛 𝚊𝚜 $$ 𝚍𝚎𝚌𝚕𝚊𝚛𝚎  𝚛𝚎𝚚_𝚙𝚊𝚝𝚑 𝚝𝚎𝚡𝚝 := 𝚌𝚞𝚛𝚛𝚎𝚗𝚝_𝚜𝚎𝚝𝚝𝚒𝚗𝚐('𝚛𝚎𝚚𝚞𝚎𝚜𝚝.𝚙𝚊𝚝𝚑', 𝚝𝚛𝚞𝚎);  𝚛𝚎𝚚_𝚓𝚠𝚝 𝚓𝚜𝚘𝚗 := 𝚗𝚞𝚕𝚕;  𝚛𝚎𝚚_𝚛𝚘𝚕𝚎 𝚝𝚎𝚡𝚝 := 𝚗𝚞𝚕𝚕; 𝚋𝚎𝚐𝚒𝚗  𝚋𝚎𝚐𝚒𝚗    𝚛𝚎𝚚_𝚓𝚠𝚝 := 𝚌𝚞𝚛𝚛𝚎𝚗𝚝_𝚜𝚎𝚝𝚝𝚒𝚗𝚐('𝚛𝚎𝚚𝚞𝚎𝚜𝚝.𝚓𝚠𝚝', 𝚝𝚛𝚞𝚎)::𝚓𝚜𝚘𝚗;    𝚛𝚎𝚚_𝚛𝚘𝚕𝚎 := 𝚛𝚎𝚚_𝚓𝚠𝚝->>'𝚛𝚘𝚕𝚎';  𝚎𝚡𝚌𝚎𝚙𝚝𝚒𝚘𝚗 𝚠𝚑𝚎𝚗 𝚘𝚝𝚑𝚎𝚛𝚜 𝚝𝚑𝚎𝚗    𝚛𝚎𝚚_𝚛𝚘𝚕𝚎 := 𝚗𝚞𝚕𝚕;  𝚎𝚗𝚍;  -- 𝙾𝚙𝚎𝚗𝙰𝙿𝙸 𝚒𝚜 𝚜𝚎𝚛𝚟𝚎𝚍 𝚊𝚝 𝙶𝙴𝚃 /𝚛𝚎𝚜𝚝/𝚟𝟷/ (𝚎𝚖𝚙𝚝𝚢 𝚙𝚊𝚝𝚑). 𝙱𝚕𝚘𝚌𝚔 𝚞𝚗𝚊𝚞𝚝𝚑 𝚌𝚊𝚕𝚕𝚎𝚛𝚜.  𝚒𝚏 (𝚛𝚎𝚚_𝚙𝚊𝚝𝚑 𝚒𝚜 𝚗𝚞𝚕𝚕 𝚘𝚛 𝚛𝚎𝚚_𝚙𝚊𝚝𝚑 = '' 𝚘𝚛 𝚛𝚎𝚚_𝚙𝚊𝚝𝚑 = '/') 𝚝𝚑𝚎𝚗    𝚒𝚏 (𝚛𝚎𝚚_𝚛𝚘𝚕𝚎 𝚒𝚜 𝚗𝚞𝚕𝚕 𝚘𝚛 𝚛𝚎𝚚_𝚛𝚘𝚕𝚎 = '' 𝚘𝚛 𝚛𝚎𝚚_𝚛𝚘𝚕𝚎 = '𝚊𝚗𝚘𝚗') 𝚝𝚑𝚎𝚗      𝚛𝚊𝚒𝚜𝚎 𝚒𝚗𝚜𝚞𝚏𝚏𝚒𝚌𝚒𝚎𝚗𝚝_𝚙𝚛𝚒𝚟𝚒𝚕𝚎𝚐𝚎 𝚞𝚜𝚒𝚗𝚐 𝚖𝚎𝚜𝚜𝚊𝚐𝚎 = '𝙽𝚘𝚝 𝚊𝚕𝚕𝚘𝚠𝚎𝚍';    𝚎𝚗𝚍 𝚒𝚏;  𝚎𝚗𝚍 𝚒𝚏; 𝚎𝚗𝚍; $$; 𝚊𝚕𝚝𝚎𝚛 𝚛𝚘𝚕𝚎 𝚊𝚞𝚝𝚑𝚎𝚗𝚝𝚒𝚌𝚊𝚝𝚘𝚛 𝚜𝚎𝚝 𝚙𝚐𝚛𝚜𝚝.𝚍𝚋_𝚙𝚛𝚎_𝚛𝚎𝚚𝚞𝚎𝚜𝚝 = '𝚙𝚞𝚋𝚕𝚒𝚌.𝚋𝚕𝚘𝚌𝚔_𝚘𝚙𝚎𝚗𝚊𝚙𝚒_𝚏𝚘𝚛_𝚊𝚗𝚘𝚗'; 𝚗𝚘𝚝𝚒𝚏𝚢 𝚙𝚐𝚛𝚜𝚝, '𝚛𝚎𝚕𝚘𝚊𝚍 𝚌𝚘𝚗𝚏𝚒𝚐';

BREAKING NEWS! No one should mistakenly think that there's only one developer working on Pi Network anymore… Because three main developers have been VERIFIED together in the OFFICIAL repository on GitHub! 1. JiaKuant1120 2. KOSASIH 3. Dr. Nikolas Kokkolis (kokkalis) – THAT'S RIGHT, the Core Developer of Pi Network! All are credited as verified contributors. The programming languages ​​also show a high-level set of technologies (TypeScript, Vue, PLpgSQL, JavaScript, etc.). Many global-level tags (UN, UNICEF, World Bank, Brazil, India, Russia, China, etc.) are also linked to the repository. The CI/CD processes, security checks, and code reviews are clearly visible in the repository. This clearly demonstrates that Pi Network is not a random project… but a well-structured, well-built project supported by multiple developers and on a global scale. People used to say, “KOSASIH or the other developers have no role in the Pi Network.” Now, the screenshots are the biggest proof—all three are contributing in the same place! The Pi Network is growing quietly but powerfully. And this repository is proof that the ecosystem is being built on an even larger scale. There's no doubt about it — this is an ecosystem validated by many developers. The future is here.

🚨 BREAKING FACT! No one should be under the misconception anymore that only one developer works on Pi Network… Because three major developers are VERIFIED together in the OFFICIAL repository on GitHub! 😳🔥 💠 1. JiaKuant1120 💠 2. KOSASIH 💠 3. Dr. Nikolas Kokkolis (kokkalis) – YES, the same Core Developer of Pi Network! 🟢 All of them are present as verified contributors. 🟢 The languages also show a high-level tech stack (TypeScript, Vue, PLpgSQL, JavaScript, etc.) 🟢 Multiple global-level tags (UN, UNICEF, World Bank, Brazil, India, Russia, China, etc.) are also linked to the repo. 🟢 Active CI/CD pipelines, security audits, and code checks are clearly visible in the repo. @PiCoreTeam

🚨 BREAKING FACT! No one should be under the misconception anymore that only one developer works on Pi Network… Because three major developers are VERIFIED together in the OFFICIAL repository on GitHub! 😳🔥 💠 1. JiaKuant1120 💠 2. KOSASIH 💠 3. Dr. Nikolas Kokkolis (kokkalis) – YES, the same Core Developer of Pi Network! 🟢 All of them are present as verified contributors. 🟢 The languages also show a high-level tech stack (TypeScript, Vue, PLpgSQL, JavaScript, etc.) 🟢 Multiple global-level tags (UN, UNICEF, World Bank, Brazil, India, Russia, China, etc.) are also linked to the repo. 🟢 Active CI/CD pipelines, security audits, and code checks are clearly visible in the repo. 🔥 This clearly shows that Pi Network is not a random project… but a fully structured, multi-developer-backed, global-scale build. 👉 People used to say: “KOSASIH or other developers have no role in Pi Network.” Now the screenshot is the biggest proof — all three are seen contributing in the same place! 💥 Pi Network is growing silently but strongly. 💥 And this repo is proof that the ecosystem is being built on an even larger scale. 📌 No more doubts — this is a multi-developer verified ecosystem. The future is loading… ⏳🚀 #PiGCV314159

something new plpgsql on top 3 😮 very active with the works

I liked the concept of Rust at first, but the syntax just looks terrible and unreadable. And I've coded in C, C , Java, Kotlin, C#, Python, PHP, JS, TS, Bash, Posix Shell, PLSQL, PLPGSQL and HLSL

Morning work session update: Modified Chatly's dashboard page code to be more clearer. Learnt how to use Supabase's SQL editor. Apparently, you need a language called plpgsql for that. So I need to learn that. Learnt about Triggers & functions in SQL. #supabase #buildinpublic

Have you compared the output of LLVM to your original code written in ActionScript, Ada, C# for .NET, Common Lisp, PicoLisp, Crystal, CUDA, D, Delphi, Dylan, Forth, Fortran, FreeBASIC, Free Pascal, Halide, Haskell, Idris, Jai (only for optimized release builds), Java bytecode, Julia, Kotlin, LabVIEW's G language, Objective-C, OpenCL, PostgreSQL's SQL and PLpgSQL, Ruby, Rust, Scala, Standard ML, Swift, Xojo, and Zig?

Next step: using C - this is just using SQL/plpgsql: github.com/andrelandgraf/rus…

Ever wondered how PostgreSQL optimizes functions? ⚡ It all comes down to VOLATILE, STABLE, IMMUTABLE🚀 Get this wrong & you could hurt performance and functionality. Broke it down with real-world examples 👇 databaserookies.wordpress.co… #PostgreSQL #Performance #plpgsql

The current top 5 most used extensions: plpgsql – 1M databases pg_stat_statements – 1M databases uuid-ossp – 80k databases pgvector – 30k databases pgcrypto – 20k databases You can see the leaderboard here: v0-neon-postgres-extensions.…

I severely underestimated the power of database user defined functions. Forgive me plpgsql, I was not familiar 🤐

syntax error reporting for plpgsql! this was a low hanging fruit but is already making my day job much more pleasant. 7/9

Data heavy logic and DB triggers. It was just more convenient to use JS over plpgsql. Took me about a week to get everything migrated over to edge functions or plpgsql depending on use case. I guess I was one of the rare ones using it.

current models write plpgsql almost without errors.