I am just a guy hitting the right note for comments of likes so you are here reading this. I am just nobody, ordinary X user, amateur part-time programmer, daily drive is Linux, Japan animate, light novel and manga lover, learning Japanese, enjoy puzzle solving.
pg_cron is a PostgreSQL extension that runs scheduled jobs inside the database using standard cron syntax. If you find you are building jobs that mostly consist of calling database commands, just let Postgres handle it with pg_cron. It is a simple, reliable, and efficient way to schedule jobs without needing an external scheduler.
Setup
If you are using a managed Postgres service, `pg_cron` is available on Crunchy Bridge and other modern Postgres providers.
If you are running Postgres yourself, you can install `pg_cron` from source or via your package manager. For example, on Ubuntu:
```
sudo apt install postgresql-18-cron
```
It must be loaded at server start via `postgresql.conf`:
```
shared_preload_libraries = 'pg_cron'
cron.database_name = 'postgres'
```
By default all jobs run in the database where the extension is installed. `cron.schedule_in_database` can target other databases on the same instance via an argument to the job creation command. Jobs run as the role that created them, and that role requires the necessary table permissions.
Getting started
After loading the extension, call `cron.schedule` to create a job. Check the documentation for exactly what you want to do, as the method is overloaded (it will behave differently and adapt for the different arguments passed). The most typical example is 3 arguments: first argument is a name for the job, the second is a cron schedule, and the third is the SQL command to run. Check the precise syntax in the documentation for what you are tryign to achieve.
[See attached images for examples of scheduling jobs.]
Managing & Monitoring Jobs
To manage jobs, query the `cron.job` table. Each row is a scheduled job, with its name, schedule, SQL command, and whether it is active.
To view a record of every execution, query `cron.job_run_details`. Each row shows when the job started, how long it ran, and whether it succeeded or failed. Failed jobs do not retry, but they do log the error and wait for the next scheduled run.
Common use cases:
• Data retention: purge old logs
• Maintenance: VACUUM a high-churn table nightly
• Aggregation: roll up hourly stats
• Archive: move old rows to a history table monthly
• Refresh materialized views
Uncommon use cases
While not every one has these problems, `pg_cron` can also be used for:
• Batching reads or writes to a remote API when paired with `http`
• ETL pipelines that offload old partitions to a data warehouse using `pg_lake`
• Use `pg_prewarm` to pre-warm a cache of frequently accessed data before daily peak traffic
Studio A-1 Pictures (Solo Leveling) reported a net profit of 91.6 million yen (~$564,000USD) for the fiscal year ending in March 2026.
Some of the studio's recent projects include:
- Solo Leveling
- 86 EIGHTY-SIX
- Lycoris Recoil
- Kaguya-sama: Love Is War
- MASHLE: MAGIC AND MUSCLES
The studio had recorded a net loss of about 178 million yen the previous year.
A 'VTuber' told everyone her 'ideal guys'. Come on. Even if this is her real view over ideal guys, then what? A cold guys came falling for her now? So?
If some cold guys fall for you, be caution, spend enough time to learn if he is really ideal for you. Do not just give in.
They make us to pay something does not worth penny, once we brought their RAMs, SSDs, phones, the same modules price drop, few years later it just worth nothing. The quality also drop.
Samsung, SK Hynix, and Micron are facing a new federal antitrust lawsuit in the US that accuses them of working together to keep DRAM production artificially low, leading to higher RAM prices.
The lawsuit claims the companies limited supply while demand continued to grow.
According to the complaint, this allowed memory prices to rise much faster creating a “RAMpocalypse.”
The lawsuit seeks class-action status and asks for damages on behalf of businesses and consumers who allegedly paid inflated prices for products containing DRAM memory.
Bunny girl enjoyers, this is for you! 👯♀️
This 1/4 Bunny Girl Hina figure from Kawa Design is everything you might want. Her beautiful long hair compliments her perfectly, and her bunny suit needs no introduction!
Order now 🖤
https://t.co/6KOQS8ML1w
The GPU Black Market documentary just hit 3 million views. Thank you, everyone. And fuck you, Bloomberg @business! For old times' sake, watch it here: https://t.co/Zk1IBDKR5m
💡 Quick Linux Tip #29
Too many log messages and looking for errors?
Try:
journalctl -p err -b
This shows only error messages from the current system boot. Instead of scrolling through thousands of log entries, Linux shows only the errors.
Here:
-p err = show only error messages
-b = show logs from the current boot
Follow @tecmint for more #LinuxTips
𝗟𝗶𝗻𝘂𝘅 𝗳𝗲𝗹𝘁 𝗶𝗺𝗽𝗼𝘀𝘀𝗶𝗯𝗹𝗲 .. 𝘂𝗻𝘁𝗶𝗹 𝗜 𝘀𝘁𝗼𝗽𝗽𝗲𝗱 𝘀𝘁𝘂𝗱𝘆𝗶𝗻𝗴 𝗶𝘁
I spent weeks memorising commands from a cheat sheet.
ls. cd. chmod. grep.
I could recite them .. But not really use then.
The moment something broke, I froze. I had visited Linux but I'd never understood it deeply.
So I wiped my laptop and installed Ubuntu.
No dual boot so no safety net. I burned the boats.
Suddenly I had to fix a missing Wi-Fi driver.
A package that failed etc. I had no other option but to go hands-on and get it to run.
That week alone taught me more than 3 months of tutorials.
Linux isn't hard, its rather easy when you learn it the right way.
Enjoy this? Repost it to your network and follow for more.
Linux users who uninstalled Windows to escape Microsoft and choose freedom with Linux may not have escaped yet.
Microsoft holds the cryptographic key that allows every major Linux distro to boot on modern hardware. Ubuntu. Fedora. Debian. All of them. Without Microsoft's signature your Linux machine does not start.
And that key expires in 4 days. June 27, 2026.
Here is what is actually happening.
When Secure Boot was introduced in 2012, Microsoft became the certificate authority for the entire PC boot ecosystem. Every Linux bootloader on the planet has to be signed by Microsoft to run on any UEFI machine with Secure Boot enabled.
Your existing Linux install will still boot after June 27. That is the good news.
The bad news is everything going forward.
→ Any new shim binary after June 27 cannot be signed with the old key anymore
→ If your firmware never gets the new 2023 Microsoft certificates, fresh distro installs will fail to boot
→ Older laptops, smaller vendor hardware and embedded devices that never receive firmware updates are now in permanent limbo
→ Dell, HP and Lenovo have pushed updates. Smaller vendors have not. Nobody knows how many devices fall through the cracks.
The fix for most people is one command: sudo fwupdmgr update
But the bigger story here is the one nobody is talking about.
The Linux community spent years arguing about freedom and independence from Microsoft. The entire time Microsoft had a key that every Linux machine on earth depended on to start.
That is not a conspiracy. That is just how Secure Boot was designed.
Run the update. Then think about what it means.
Full details here:
https://t.co/Vn7A4TPjrC