radimm

8 ms·

61.
by radimm 11mo ago
The primary direction is to make RegreSQL part of CI/CD pipelines. In theory in can be run against production DB, but I believe it needs much more work to provide real value there. Thank you for the comment!
62.
by radimm 11mo ago
OP here - I do agree some of the problems that come with SQL/ORM queries are pretty horrendous and that's exactly where I would like RegreSQL going. For now I can't promise the particular direction, but comments like this are
63.
RegreSQL: Regression Testing for PostgreSQL Queries(boringsql.com)
151 points by radimm 11mo ago|38 comments
64.
Beyond Start and End: PostgreSQL Range Types(boringsql.com)
2 points by radimm 11mo ago|0 comments
65.
by radimm 1y ago
this is same with GCP Cloud SQL and RDS (there I need to double check). They really don't want you to access the underlying FS.
66.
PostgreSQL Maintenance Without Superuser(boringsql.com)
80 points by radimm 1y ago|5 comments
67.
Beyond the Basics of Logical Replication(boringsql.com)
2 points by radimm 1y ago|0 comments
68.
First Steps with Logical Replication in PostgreSQL(boringsql.com)
2 points by radimm 1y ago|0 comments
69.
PostgreSQL Service Connections(boringsql.com)
3 points by radimm 1y ago|0 comments
70.
by radimm 2y ago
Lived through it and while it might be similar, Microsoft had monopoly at that point (90% and higher share in personal computers - depending on the market). Apple is nowhere near that.
71.
Why PostgreSQL major version upgrades are hard(peter.eisentraut.org)
1 points by radimm 2y ago|0 comments
72.
DELETEs Are Difficult(notso.boringsql.com)
139 points by radimm 2y ago|115 comments
73.
Beyond Simple Upserts with Merge in PostgreSQL(notso.boringsql.com)
1 points by radimm 2y ago|0 comments
74.
Gentle Introduction to Window Functions in PostgreSQL(notso.boringsql.com)
2 points by radimm 2y ago|0 comments
75.
by radimm 2y ago
That’s PGRX - not PostgreSQL
76.
by radimm 2y ago
Author here, I hope I made it clear pg_cron is available everywhere. Thank you for pg_cron though!
77.
by radimm 2y ago
Autor here. Generally I feel much more confident about external services 'pulling' the status. But I have something cooking up to reduce the friction of external calls and possible process blocking...
78.
The time keepers: pg_cron and pg_timetable(notso.boringsql.com)
123 points by radimm 2y ago|17 comments
79.
by radimm 2y ago
You are not wrong here. This is what I'm trying to get to with boringSQL - create more 'packaging' around things to improve developer UX while developing SQL based solutions. Be it APIs, complex apps and everything around.
80.
by radimm 2y ago
Yes, application issues own JWT tokens - specifically in `public.create_jwt`
81.
by radimm 2y ago
Author here - you are absolutely correct. Damn, during the last proof-reading one function got lost. Will fix it ASAP
82.
PostgREST Tutorial: APIs made easy(notso.boringsql.com)
27 points by radimm 2y ago|18 comments
83.
Custom PostgreSQL Extensions with Rust(notso.boringsql.com)
1 points by radimm 2y ago|0 comments
84.
Scaling Clubhouse From 10K to 10M Users In 6 Months With Postgres(stepchange.work)
16 points by radimm 2y ago|3 comments
85.
by radimm 2y ago
Thank you for correction! Indeed - it's one of those things i've read but practically avoided it for historic reasons and therefore forgot about it.
86.
by radimm 2y ago
Author here - this is my primary goal, exposing the complexity developer might not even think about. Can't even count number of instances seemingly inconspicuous changes caused incident. "Works on my DB" is new "works on
87.
How not to change PostgreSQL column type(notso.boringsql.com)
1 points by radimm 2y ago|0 comments
88.
by radimm 2y ago
On other hand index bloat can be solved relatively easily using concurrent reindex (since 12.x if I remember correctly).
89.
by radimm 2y ago
Thanks for the good point. You are right, pg_squeeze is not available there. Will update post tonight for clarity. I know it's available on GCP though.
90.
by radimm 2y ago
Consider time it takes to rewrite the table, downtime you can afford and the disk space you have. My goal is to write bit more about the cases that go beyond the usual "works on my 100MB" scenario.

More ›