Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
uhoh-itsmaciek
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
91.
▲
by
uhoh-itsmaciek
4y ago
There are some other cons: Memory usage and I/O can be less efficient. Postgres handles table data in 8kb pages, so even if you're just reading a single row, that reads 8kb from disk and puts 8kb in the Postgres buffer cache, with
92.
▲
by
uhoh-itsmaciek
4y ago
For what it's worth, there is currently some active work in this area [1]. It's too late for 15, but it might land in 16 (next fall). [1]: https://www.postgresql.org/message-id/flat/20220628083230.c4...
93.
▲
by
uhoh-itsmaciek
4y ago
American country music has been heavily influenced by African Americans since the beginning (often without recognition, though that's starting to change.) The banjo is based on African instruments, and many musicians like Huddie Ledbet
94.
▲
by
uhoh-itsmaciek
4y ago
Any list like this will have omissions, but yeah, Gattaca is great. Primer should be there, too.
95.
▲
by
uhoh-itsmaciek
4y ago
>Variable length strings are kept in a separate file (TOAST tables), referenced by the tuple. This keeps records fixed size... That's not entirely true: variable-width row values under a size threshold are stored inline (possibly co
96.
▲
by
uhoh-itsmaciek
4y ago
There's a pretty good high-level overview of the implementation details in the official docs: https://www.postgresql.org/docs/current/storage.html
97.
▲
by
uhoh-itsmaciek
4y ago
Sequel [1], the Ruby ORM. It's rock-solid, provides similar abstractions to Active Record but feels much better thought out, and it has great docs. Also, at any point in time, it's likely to have zero open issues and zero open pul
98.
▲
by
uhoh-itsmaciek
4y ago
I don't see anything in the 2022 blog post that contradicts the 2014 mailing list post. These are different features with different trade-offs and somewhat overlapping use cases.
99.
▲
by
uhoh-itsmaciek
4y ago
They're not really the same thing: https://www.postgresql.org/message-id/CAM3SWZRP0c3g6+aJ=YYDG...
100.
▲
by
uhoh-itsmaciek
4y ago
No problem. In country and bluegrass jamming circles, there's definitely a faction that prefers simpler songs with fewer chords (true to Howard's quote), so I was amused to see his words distorted. Thanks for fixing it.
101.
▲
by
uhoh-itsmaciek
4y ago
Three chords and the truth. Usually attributed to Harlan Howard [1], an early country music songwriter. A lot of early country music sticks to just I, IV, and V. [1]: (PDF) https://countrymusichalloffame.org/content/u
102.
▲
by
uhoh-itsmaciek
5y ago
As some other replies noted, Postgres does not support that. Some drivers or ORMs do their own pre-processing on query text, and add their own support for that. E.g., in ActiveRecord, you can do: User.where("status = ?", &qu
103.
▲
by
uhoh-itsmaciek
5y ago
Yeah, this is generally a good compromise. I sometimes like to write these as helper components instead: <Layout> <Header /> <Content page={page} /> <Footer /> </Layout>
104.
▲
by
uhoh-itsmaciek
5y ago
Right, Postgres supports this use case explicitly with INCLUDE [1], which can be more efficient than just indexing all the columns you need. Pretty sure SQL Server has something similar. [1]: https://www.postgresql.org/docs&
105.
▲
by
uhoh-itsmaciek
5y ago
I don't know. I'm not very familiar with Next.js (I'd heard about it but never really looked into it much). Your response inspired me to investigate, and I found an article by a Remix founder about the differences [1]. It
106.
▲
by
uhoh-itsmaciek
5y ago
I think it's exciting to see frameworks like https://remix.run/ trying to temper the disadvantages of SPAs by relying on web standards and server-side rendering. It's pretty cool that this is a JavaScript framewor
107.
▲
by
uhoh-itsmaciek
5y ago
Note that SQL-standard bodies are supported as of 14 [1]: Allow SQL-language functions and procedures to use SQL-standard function bodies (Peter Eisentraut) Previously only string-literal function bodies were supported. When writ
108.
▲
by
uhoh-itsmaciek
5y ago
This post glosses over it, but larger fields are stored via the TOAST mechanism [1], which does support compression. [1]: https://www.postgresql.org/docs/current/storage-toast.html
109.
▲
by
uhoh-itsmaciek
5y ago
Check out https://fretboard.cool and tell me what tunings to add! Or submit a PR [1]. [1]: https://github.com/uhoh-itsmaciek/fretboard.cool/blob/master... (there's a quirk noted in the TODO t
110.
▲
by
uhoh-itsmaciek
5y ago
Neat! If anyone wants to check out a very, very basic version of a similar idea, I built https://fretboard.cool a couple of years ago.
111.
▲
by
uhoh-itsmaciek
5y ago
If anyone wants to keep up with Tom Lane's prolific mailing list contributions without subscribing to the pgsql-hackers firehose, I wrote a Twitter bot that tweets the last sentence (according to some mostly-working regex heuristics) f
112.
▲
by
uhoh-itsmaciek
5y ago
Due to some Postgres limitations, a query can run even after the connection drops (the backend process only checks if there's still a client to send results to after query completion). I think I saw some work being done on this in 14 o
113.
▲
by
uhoh-itsmaciek
5y ago
I think there's a case to be made that a timeout is more important. With an OLTP workload, it's not hard to imagine a runaway query running for days, consuming I/O bandwidth and silently slowing everything down. A timeout may
114.
▲
by
uhoh-itsmaciek
5y ago
It should, but it may need to be tuned to run aggressively enough, which can be tricky. Sometimes it's easier to just schedule a manual job that runs during your off hours. There are some interesting discussions on the Postgres develop
115.
▲
by
uhoh-itsmaciek
5y ago
Also not working here on FF/Linux. Tried Chrome and it's pretty nice. One odd thing I noticed: if I click on an image and then click left or right to go forward or back, after mouse down but before mouse up, the picture index show
116.
▲
by
uhoh-itsmaciek
5y ago
I love having the context from a good set of liner notes. Session dates, musicians, back story. It anchors the music as work done by real people, and not just content to consume. I don't really care about the physical discs, but it see
117.
▲
by
uhoh-itsmaciek
5y ago
Another favor you should do yourself is use bigint keys (unless using uuid as suggested elsewhere, or you're very, very sure you'll never chew through 2 billion ids).
118.
▲
by
uhoh-itsmaciek
5y ago
Those are great. Another memorable NYT one had the theme A SHOT IN THE DARK, and several answers ended in SHOT (RIMSHOT, EARSHOT, etc.), but the grid only had space for the first part of the word, so the actual answers were RIM⬛, EAR⬛, etc.
119.
▲
by
uhoh-itsmaciek
5y ago
Ah, so not sure how you're checking, but it looks like your thresholds might be just too aggressive: it looks like my window.innerHeight < 1024 [1] and that's probably triggering the warning. [1]: https://developer.m
120.
▲
by
uhoh-itsmaciek
5y ago
Neat! Thanks for sharing. >Note: This visualization was designed for screens larger than 1024 x 1024 and for desktop-style interactions. Why am I getting this warning on my 4K UHD display? Both Firefox 89 and Chrome 91 on Ubuntu.
More ›