Lightnews — Scholar-powered news

LightNews

Vik Fearing

@vik.thegresqlpost.org

190 followers 110 following 360 posts

Member of the ISO/IEC working group for SQL. Performance is an implementation detail. HUGE fan of MLB and WFTDA, and pretty much not interested in any other sport. he/him by default but will happily answer to anything. A cheeseburger in paradise. #IYKYK

Posts Media Videos Starter Packs

Vik Fearing @vik.thegresqlpost.org · 21h

If you're parsing postgres's text representation of arrays, are you handling custom separators?

For example, the box type uses ';' instead of ',' and any custom type can choose their own.

Vik Fearing @vik.thegresqlpost.org · 2d

Now that you know it exists, you have to implement it in @jooq.org. I don’t make the rules.

Vik Fearing @vik.thegresqlpost.org · 2d

The bounds get lost during pretty much any operation. One day I will go spelunking to see why this exists in the first place.

#PostgreSQLQuirks

Vik Fearing @vik.thegresqlpost.org · 3d

My indexing starts where I tell it to.

VALUES ((CAST('[-1:1]={1,2,3}' AS INTEGER ARRAY))[0])

=> 2

Reposted by Vik Fearing

Arthur Clune @clune.org · 6d

Also Claude, 🔥

Output from Claude: "The verbosity you'll encounter isn't accidental; it's COBOL heritage, designed for business analysts to supposedly read. Whether that goal was achieved is debatable."

Reposted by Vik Fearing

Data Code 101 @datacode101.bsky.social · 6d

Edgar F. Codd. In 1970, working at IBM, Codd published his paper, “A Relational Model of Data for Large Shared Data Banks.” It introduced a new model for managing data, now accepted as the dominant approach for Relational Database Management Systems (RDBMS).
www.seas.upenn.edu/~zives/03f/c...
#sql

www.seas.upenn.edu

Vik Fearing @vik.thegresqlpost.org · 7d

Yes. You can change the default storage properties for a lot of data types, but it only operates on single values.

Vik Fearing @vik.thegresqlpost.org · 7d

They are not compressed. Certain values might be (see TOAST) but not the page itself.

Reposted by Vik Fearing

ليثيوم @lithium-rose.at.app.wafrn.net · 8d

I hate SQL

Vik Fearing @vik.thegresqlpost.org · 12d

My calendar only goes up to 12 months, so this must be fake news.

Merriam-Webster @merriam-webster.com · 12d

We are thrilled to announce that our NEW Large Language Model will be released on 11.18.25.

Vik Fearing @vik.thegresqlpost.org · 17d

Then what is it?

Vik Fearing @vik.thegresqlpost.org · 17d

Which is exactly the wrong time to start testing. At the very latest you should have been testing RC1.

Vik Fearing @vik.thegresqlpost.org · 18d

Why would you only start testing now? You should have been testing weeks ago!

Vik Fearing @vik.thegresqlpost.org · 18d

www.postgresql.org/about/news/p...

PostgreSQL 18 Released!

The [PostgreSQL Global Development Group](https://www.postgresql.org) today announced the release of [PostgreSQL 18](https://www.postgresql.org/docs/18/release-18.html), the latest version of the worl...

www.postgresql.org

Vik Fearing @vik.thegresqlpost.org · 22d

huh?

Vik Fearing @vik.thegresqlpost.org · 24d

Simple solution: don't migrate!

Vik Fearing @vik.thegresqlpost.org · 24d

Correct. We write SQL for fun (and profits).

Reposted by Vik Fearing

Klaus Aschenbrenner @sqlpassion.at · 26d

Postgres is Too Good (And Why That's Actually a Problem): dev.to/shayy/postgr... #PostgreSQL

Postgres is Too Good (And Why That's Actually a Problem)

We need to talk about something that's been bothering me for months. I've been watching indie hackers...

Vik Fearing @vik.thegresqlpost.org · 26d

Why PostgreSQL indexes feel like magic (and when they backfire)

toxigon.com/understandin...

Reposted by Vik Fearing

StasB @stasb.bsky.social · 27d

Did you know you could compare multiple fields at a time in #SQL?

Vik Fearing @vik.thegresqlpost.org · 27d

I did know that. 😜

Reposted by Vik Fearing

davidi @davidi99.bsky.social · 28d

13 reasons SQL has got to go (but never will?)

13 reasons SQL has got to go

Why is the language developers and DBAs use to organize data such a mess? Here are 13 reasons we wish we could quit SQL, even though we probably won't.

www.infoworld.com

Vik Fearing @vik.thegresqlpost.org · Sep 13

*open source

Vik Fearing @vik.thegresqlpost.org · Sep 13

On DROP?

Anyway, requiring a WHERE on DELETE does nothing, you can always write WHERE TRUE.