samokhvalov

5 ms·

1.
Growth of CVEs fixed in Postgres looks exponential(twitter.com)
5 points by samokhvalov 1mo ago|2 comments
2.
by samokhvalov 2mo ago
it was silly, quick check out of curiosity what Opus 5 can do – and the first thing I saw was so impressive that it made me spend hours during weekend polishing it here it is from history, without edits > you're a veteran Postgres h
3.
by samokhvalov 2mo ago
correct on both counts
4.
by samokhvalov 2mo ago
yeah, it was there before your comment; maybe not easy to find (help is on "?", which is also maybe not easy to find)
5.
by samokhvalov 2mo ago
yep (via pressing T) but I agree, could be better – thinking
6.
by samokhvalov 2mo ago
try pressing T
7.
by samokhvalov 2mo ago
Correct -- z-fighting on coplanar ground surfaces. Fixing with explicit offsets. thanks
8.
by samokhvalov 2mo ago
I hear you. WIP! thanks for all the feedback. It's amazing for me too. It all started yesterday with a single prompt and curiosity what Opus 5 can do. ~3.86B tokens used so far (not counting GPT 5.6 Sol that at some point started to do
9.
PGSimCity – an explorable 3D model that shows how Postgres works(github.com)
38 points by samokhvalov 2mo ago|3 comments
10.
by samokhvalov 4mo ago
Hey, PostgresAI founder here. thank you for using DBLab Can you DM me, please? Really curious about your experience
11.
Pg_flight_recorder – server-side flight recorder for Postgres(github.com)
2 points by samokhvalov 4mo ago|0 comments
12.
by samokhvalov 5mo ago
thank you!
13.
by samokhvalov 5mo ago
thanks for pushing back, by the way – I'm thinking this thru, and will likely rename fun fact: I now think, "River" (Go project) is also a misleading name for a task queue system :)
14.
by samokhvalov 5mo ago
1. partitions are never dropped – they got TRUNCATEd (gracefully) during rotation 2. INSERT-only. Each consumer remembers its position – ID of the last event consumed. This pointer shifts independently for each consumer. It's much clos
15.
by samokhvalov 5mo ago
you need to explain claude code that PG18 is out already ;)
16.
by samokhvalov 5mo ago
Fair. I had an attempt to clarify it in README that PgQue is "closer to Kafka topics than to a job queue" -- per-subscription cursor on a shared event log, no ACK-delete, no visibility timeout. That makes PgQue an event-streaming
17.
by samokhvalov 5mo ago
correct it's explained in README: > Category: River, Que, and pg-boss (and Oban, graphile-worker, solid_queue, good_job) are job queue frameworks. PgQue is an event/message queue optimized for high-throughput streaming with fan
18.
by samokhvalov 5mo ago
nice work I wonder if you considered WAL-G, which is also written in Go and has this: https://github.com/wal-g/wal-g/blob/master/docs/PostgreSQL.m...
19.
by samokhvalov 5mo ago
Taxonomy is correct. But the benefit isn't "table grows indefinitely vs. vacuum-starved death spiral" in all three approaches, if the consumer falls behind, events accumulate The real distinction is cost per event under MVCC
20.
by samokhvalov 5mo ago
(PgQue author here) I didn't understand nuances in the beginning myself We have 3 kinds of latencies when dealing with event messages: 1. producer latency – how long does it take to insert an event message? 2. subscriber latency – how
21.
pg_ash: See what your Postgres was busy with recently(github.com)
2 points by samokhvalov 7mo ago|0 comments
22.
by samokhvalov 8mo ago
congrats! the more postgres everywhere, the better
23.
Select FOR UPDATE considered harmful in PostgreSQL(cybertec-postgresql.com)
44 points by samokhvalov 1y ago|2 comments
24.
by samokhvalov 1y ago
1) built using an open source kubernetes operator, as I understand 2) Crunchy provides true superuser access and access to physical backups – that's huge
25.
by samokhvalov 1y ago
I also don't see any good reasons for this.
26.
by samokhvalov 1y ago
> we deploy the Postgres instances on Kubernetes via the CloudNativePG operator. I'm curious if split brain cases already experienced. At scale, it should be so https://github.com/cloudnative-pg/cloudnative-pg&#
27.
Vertical Sharding Sucks(pgdog.dev)
20 points by samokhvalov 1y ago|13 comments
28.
by samokhvalov 2y ago
Thanks for mentioning!
29.
Impact of Partitioning on Planning Time in Postgres(postgres.ai)
1 points by samokhvalov 2y ago|0 comments
30.
Number of partitions vs. planning time in Postgres(postgres.ai)
1 points by samokhvalov 2y ago|0 comments

More ›