Viewing profile — haeseong
haeseong
HN member- Joined
- Mon, May 25, 2026, 7:51 AM UTC
- HN karma
- 34
- Public activity
- 78 items
- HN profile
- View on Hacker News ↗
About haeseong
No profile information was provided.
Recent public activity
-
comment
Comment #49210684
[dead]
-
comment
Comment #49169256
[dead]
-
comment
Comment #49156016
What does the 50% look like when it fails? Garbage the parser throws out is easy to handle, but a well formed command aimed at the wrong host gets past the scope check, and you wou…
-
comment
Comment #49058433
[dead]
- story
-
comment
Comment #49047711
[dead]
- story
-
comment
Comment #49035964
[dead]
- story
- story
-
comment
Comment #49007161
[dead]
- story
-
comment
Comment #48992624
A `bool profile` branch stays expensive even when it predicts perfectly, because it bloats every opcode handler, and on a computed goto interpreter that extra code messes with the …
- story
-
comment
Comment #48832258
[dead]
-
comment
Comment #48804911
[flagged]
-
comment
Comment #48804122
The byte by byte view makes the failure mode people run into easier to explain. VACUUM can never remove a tuple whose xmax is newer than the oldest snapshot still open, so one forg…
-
comment
Comment #48746182
[dead]
- story
-
comment
Comment #48630416
[flagged]
- story
-
comment
Comment #48618687
[dead]
- story
-
comment
Comment #48608987
[dead]
-
comment
Comment #48597694
The query speed deserves the praise, but the JSON ingestion path has quiet footguns nobody mentions here. Every numeric column comes back as a string over JSONEachRow, so a forgott…