E
End Point Blog
blog.endpoint.com · Company blog · on HN since 2009
End Point is a consultancy whose engineers write practical posts on PostgreSQL, Linux sysadmin, devops and NoSQL.
What HN saysHN commenters link it for practical tips, such as GNU Screen follow-the-leader, Postgres prepared statement plans and foreign data wrappers. One author calls the posts useful.
33HN people shared it
10linked it in comments
79stories submitted
441story points
9 years agolast shared
2009people per year2026
Most-shared posts
- 1State of the Postgres project2 people · 70 points · first shared 2010 · 25 comments on HN
- 2PostgreSQL as NoSQL with Data Validation2 people · 3 points · first shared 2013 · discussion on HN
- 3"Follow the Leader" with GNU Screen2 people · 1 points · first shared 2009 · discussion on HN
- 4Bucardo 5, async replication for PostgreSQL with true multi-master1 people · 147 points · first shared 2014 · 18 comments on HN
- 5Mysql and psql command equivalents table1 people · 21 points · first shared 2009 · discussion on HN
- 6Python string formatting and UTF-8 problems workaround1 people · 13 points · first shared 2015 · 8 comments on HN
- 7NoSQL Live: The Dynamo Derivatives (Cassandra, Voldemort, Riak)1 people · 7 points · first shared 2010 · discussion on HN
- 8How to Bring a Baby to a Tech Conference1 people · 7 points · first shared 2015 · discussion on HN
- 9A few PostgreSQL tricks1 people · 6 points · first shared 2015 · discussion on HN
- 10Selectively firing Postgres triggers1 people · 6 points · first shared 2015 · discussion on HN
- 11Graphing System Statistics with Grafana1 people · 5 points · first shared 2015 · discussion on HN
- 12Utah Open Source Conference 20101 people · 5 points · first shared 2010 · discussion on HN
- 13Angular Responsive Layout Directive1 people · 4 points · first shared 2015 · discussion on HN
- 14MediaWiki complete test wiki via cloning1 people · 4 points · first shared 2015 · discussion on HN
- 15Documenting Web Services with Perl POD and AJAX1 people · 4 points · first shared 2015 · discussion on HN
What HN people wrote when they linked it
blimpy · 2017-04-21
My co-workers at End Point write some pretty useful posts, with a lot of practical ones around Linux sysadmin and devops topics:
http://blog.endpoint.com/
A bit self-promotional since I blog there too, but I'm greatly outnumbered.
chrissnell · 2017-01-25
Another way, using only software that you have already: get your friends' public keys and make a burner account on any jointly-reachable server/laptop/whatever and do a follow-the-leader screen:
http://blog.endpoint.com/2009/09/gnu-screen-follow-leader.html
greenleafjacob · 2016-06-26
Here is an example [1] that just is a simple equality comparison on an indexed column falling back to a sequential table scan.
[1] http://blog.endpoint.com/2014/04/custom-plans-prepared-statements-in.h…
prats226 · 2016-02-14
I found a new workflow called skullcandy workflow which has separate QA branch. So trying out that for a while. Only downside is you have to do accounting of which branches were merged to QA and were successful and then again merge them to dev, instead of reverting from dev.
http://blog.endpoint.com/2014/05/git-workflows-that-work.html
snaky · 2013-05-13
But now we can have both - PostgreSQL with all the batteries + (as just one of that batteries) any additional NoSQL backend using http://blog.endpoint.com/2013/05/foreign-data-wrappers.html
imglorp · 2013-02-06
Um, with (2) you're kind of supporting Jamie's point because PostgreSQL's bug system has plenty of drawbacks. While yes there is an outstanding and responsive community, its cultural bug knowledge is stored in a mailing list here: http://www.postgresql.org/support.
Greg at End Point thrashed this system better than I can, two years ago: http://blog.endpoint.com/2011/05/postgres-bug-tracking-help-wanted.htm… (TLDR: no metadata, no workflows)
brianbuchalter · 2013-01-11
I've found a lot of the posts so far to not cover both how to use Metasploit and actual secure a site. So I wrote http://blog.endpoint.com/2013/01/rails-CVE-2013-0156-metasploit.html.
hector_ka · 2010-11-16
Since I am looking for a platform myself , and I asked on HN about Spree option , here is something:
http://blog.endpoint.com/2010/06/spree-vs-magento-feature-list.html
tomdale · 2014-11-03
Needless to say, we’re incredibly excited about this release. If you’re in a hurry, you can just skim; the bolded sentences and code samples are the important takeaways.
The reason this is so long is that we’re doing the 2.0 release through our community RFC process[1]. Change can be scary when you’ve made serious investment in an open source tool, so we want to provide as much detail as we can while leaving open the opportunity to incorporate feedback.
I’d like to thank the members of the Ember core team, who paid out of pocket to spend this past weekend with me in Chicago for the face-to-face meeting where we banged out all of these details. Maintaining an indie open source project can be painful at times, but I think history demonstrates there’s no better way to foster a project that is as aligned with the goals of its users as possible.[2]
[1]: https://github.com/emberjs/rfcs
[2]: http://blog.endpoint.com/2010/01/state-of-postgres-project.html
aidos · 2014-03-13
Thanks for the info - I'm thinking more along the lines of constraining the data within the valid json.
Just found this post which shows how you can do it.
CREATE TABLE products (
data JSON,
CONSTRAINT validate_id CHECK ((data->>'id')::integer >= 1 AND (data->>'id') IS NOT NULL ),
CONSTRAINT validate_name CHECK (length(data->>'name') > 0 AND (data->>'name') IS NOT NULL ),
CONSTRAINT validate_description CHECK (length(data->>'description') > 0 AND (data->>'description') IS NOT NULL ),
CONSTRAINT validate_price CHECK ((data->>'price')::decimal >= 0.0 AND (data->>'price') IS NOT NULL),
CONSTRAINT validate_currency CHECK (data->>'currency' = 'dollars' AND (data->>'currency') IS NOT NULL),
CONSTRAINT validate_in_stock CHECK ((data->>'in_stock')::integer >= 0 AND (data->>'in_stock') IS NOT NULL )
}
http://blog.endpoint.com/2013/06/postgresql-as-nosql-with-data-validat…