Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
keithgabryelski
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
31.
▲
A spin lock in C that does not require a machine level exchange instruction
(github.com)
21 points
by
keithgabryelski
12y ago
|
25 comments
32.
▲
Ensuring synchronous DDL operations on tables being replaced in Redshift?
(stackoverflow.com)
1 points
by
keithgabryelski
12y ago
|
0 comments
33.
▲
by
keithgabryelski
12y ago
yes, the parent is also a target table -- but for partitioning you never put anything in the parent. I could probably talk about the troubles of putting data in the parent table. and yes, a trigger function is possible -- and I could have
34.
▲
by
keithgabryelski
12y ago
it's simply not a problem in practice -- even for very very large tables. Use bigserial if you must. you can also modify the child table to use a different sequence for each table.
35.
▲
by
keithgabryelski
12y ago
Well, that is about the best compliment I've every heard. thank you!
36.
▲
by
keithgabryelski
12y ago
you could -- that isn't "partitioning" in the way I discuss it in the linked article when it is split across machines it is generally referred to as sharding: http://en.wikipedia.org/wiki/Shard_(database_
37.
▲
by
keithgabryelski
12y ago
if I understand you correctly, this type of thing is implemented by partitioning by hour in a day and then having a janitor process drop tables that are older than 24 hours.
38.
▲
by
keithgabryelski
12y ago
i suspect this was the simple solution that the postgresql team could implement easily. that is actually why i wrote the partitioned gem (which this explanation is apart of): https://github.com/fiksu/partitioned the la
39.
▲
PostgreSQL partitioning explained
(github.com)
228 points
by
keithgabryelski
12y ago
|
33 comments
40.
▲
by
keithgabryelski
12y ago
testing a connection for various features is not as robust as actually trying the operation you want to complete and determining if it worked. drop all the extra work and let code fail gracefully while in action.
41.
▲
by
keithgabryelski
13y ago
gosh, i see this "weird allocator trick" to be exceptionally insightful as to the possible attacks that and likely vulnerabilities that may be introduced into code. One of the biggest issues for a development team isn't how t
42.
▲
by
keithgabryelski
13y ago
it's time for the community (and possible all major opensource projects) to have code review parties. 1 week before, a module is declared the subject. at the time of the party, the major owners are on the hook for function by function
43.
▲
What to tell your non-technical friends and family about HeartBleed
(keithgabryelski.blogspot.com)
4 points
by
keithgabryelski
13y ago
|
0 comments
44.
▲
by
keithgabryelski
13y ago
the lesson: general and up-to-date understanding of larger systems is sometimes required to make the most innocuous changes. be a generalist keep up on current technologies
45.
▲
by
keithgabryelski
13y ago
It's odd that at the top of the article the author claims Pandora might be a scientist or a librarian (but they won't reveal such things) Then later claims they looked at the hidden link because they were curious (because scientis
46.
▲
by
keithgabryelski
13y ago
I disagree with the author that the programmer can't interpret longer than 80 lines. we don't read programs like a 6 year old sounds out words. We read more like a 10 year old (and above) by sighting tokens. Simply put: the worl
47.
▲
by
keithgabryelski
13y ago
http://en.wikipedia.org/wiki/Banknote#Early_Chinese_paper_mo... 7th century Chinese bank notes.
48.
▲
by
keithgabryelski
13y ago
Simple certainly is good. It requires technology to create the notes but none to transfer them. There is goodness in this. Hey, the lights are out -- can I buy some water from you -- my family is thirsty -- no? sorry, not until the the in
49.
▲
by
keithgabryelski
13y ago
go home bitcoin -- you're drunk. bank notes are a very simple system, so simple it has been used for over a thousand years.
50.
▲
by
keithgabryelski
13y ago
To work in AWS's system you must have redundant nodes -- such that any single node can be rebooted without affecting the system as a whole. Notification that your system is on old hardware that has been deprecated is part of the price
51.
▲
by
keithgabryelski
13y ago
There is a job at Google to ask legendary-coders coding questions. It is reasonable.
52.
▲
by
keithgabryelski
13y ago
My observation is that a lot of interviews come down to "stump the chump" questions; a question that is meant to show a single issue the interviewee has under their belt and is used to gauge the entirety of the interviewer's
53.
▲
by
keithgabryelski
13y ago
I can't edit the previous post for some reason, so i'll post it again: http://imgur.com/bOPQkOI.jpg http://imgur.com/mjv4kzI.jpg http://imgur.com/FZ3d8Jv.jpg http://img
54.
▲
by
keithgabryelski
13y ago
It's not obvious to me what the problem is. Maybe google drive doesn't like the number of hits it got to this one area. In any case, this is the base directory: https://googledrive.com/host/0B_Y4OBMHA7qRaTBGbV
55.
▲
by
keithgabryelski
13y ago
https://googledrive.com/host/0B_Y4OBMHA7qRaTBGbVNaVFlYWWM/im... https://googledrive.com/host/0B_Y4OBMHA7qRaTBGbVNaVFlYWWM/im... https://googledrive.com/host/0B_Y4OBM
56.
▲
by
keithgabryelski
13y ago
I also don't see a schema that is tuned for redshift. There is no description of a sortkey or a distribution key (let alone which compression encoding was used) And at least for the first query you could use UNLOAD instead of select (d
57.
▲
by
keithgabryelski
13y ago
when you pretend you aren't using regular expressions, then you have two problems.
58.
▲
by
keithgabryelski
14y ago
This is more akin to copying someone's math test and not having enough understanding of the English language to avoid copying the "Name: Keith Gabryelski" in the upper right hand corner Stealing a design/style or color scheme would yield a
59.
▲
by
keithgabryelski
14y ago
or just accept that TLDR means more than what your narrow definition and current pet peeve would otherwise allow?
60.
▲
by
keithgabryelski
14y ago
There is a reason the world doesn't scroll this way. It looks horrible and adds no real value. A split screen with smooth scrolling is far superior and far more natural UI
More ›