sickpig
Quick list of major features:
Parallel sequential scans, joins and aggregates
Elimination of repetitive scanning of old data by autovacuum
Synchronous replication now allows multiple standby servers for increased reliability
Full-text search for phrases
Support for remote joins, sorts, and updates in postgres_fdw
Substantial performance improvements, especially in the area of improving scalability on many-CPU servers
"luckily we recovered almost all data!"
On the other hand median just gives you the value that split the distribution in two exact parts.
Price/Income distributions are the perfect match if you want to see avg bias taken to its extreme.
e.g.
median of [2,2,2,2,2,2,2,100] = 2 average of [2,2,2,2,2,2,2,100] = 14.25
Postgresql:Generate parallel sequential scan plans in simple cases
PP is used when a system, in this case the humanity, is at risk of total failure, i.e. ruin.
Quoting the first paragraph of the paper:
The precautionary principle (PP) states that if an action or policy has a suspected risk of causing severe harm to the public domain (affecting general health or the environment globally), the action should not be taken in the absence of scientific near-certainty about its safety. Under these conditions, the burden of proof about absence of harm falls on those proposing an action, not those opposing it. PP is intended to deal with uncertainty and risk in cases where the absence of evidence and the incompleteness of scientific knowledge carries profound implications and in the presence of risks of "black swans", unforeseen and unforeseable events of extreme consequence.
Quick someone tell the federal reserve / ecb that QEs can't be used because they are an oxymoron (sorry can't resist).
That said it is possible to have an open ledger used to avoid duble spends without revealing anything about someone finance, just look for monero (xmr) or zerocash.
That said I think jurnos really like this kind of narrative and subject, since it's really appealing to theirs audience.
It's a sort feedback loop that time will help to "break".
See:
https://news.ycombinator.com/item?id=9371854
https://news.ycombinator.com/item?id=9375978
It seems to be a real hot-button to say the least.
There's still a somewhat annoying limitation that is related to the status of table partitioning in postgresql.
In fact the planner automatically choose the right child table, be it on the same db or into another server, for UPDATE and SELECT statements but not for INSERTs. This is a known limitation and there's active work to fix it but don't hold your breath though.
PostgreSQL 9.5 will have native sharding
Joking aside, I think that using prisons just for isolation is a waste of tax payer money.
Just think about at the case at hand, we are wasting the money needed to keep this guy in jail for another 8 decades with no actual reasons.
edit: fix grammar
Really? I thought it was about correcting/reforming.
I've recently read a proposal for such a scheme written by Justus Ranvier, you can find it here:
https://bitcoinism.liberty.me/2015/02/09/economic-fallacies-...
tl;dr Bitcoin peer-to-peer (P2P) network needs price discovery built directly into it through micropayment channels (https://bitcoinj.github.io/working-with-micropayments)
Bitcoin core latest version (0.10.0) have reduced significantly the bootstrap time of a node (e.g. through "header-first" mechanism).
Future releases will introduce other improvements that will lead to a reduction in terms of network bandwidth/latency (O(1) block propagation, IBLT) and IO space (e.g. pruning)
That said it's true there's no economic incentives in place to "just" run a full node. Person that run full nodes does that for a lot of reasons modulo the economic one.
Hence the number of full nodes is steadily declining http://www.bitcoinpulse.com/#/chart/bitnodes/num_nodes
There are proposals (1) floating around to fix the situation through, guess what... economic incentives, but we are for from getting some sort of agreement, worse than that I dare say that in this case we're still struggling with problem awareness.
(1) https://bitcoinism.liberty.me/2015/02/09/economic-fallacies-...
He admits the models will never be perfect, but thinks that even a model that’s only right about 50 percent of the time could help investors and entrepreneurs avoid particularly bad ideas
dunno why but I can't stop thinking that tossing a coin could achieve the same goal :)
Having said that your consideration about "on line nature" applies also to my mastercard in almost all the shops I usually buy stuff be it on line or off line. Without me providing the OTP and the payment processor verifying it I can't buy anything.
A little bit OT but worthy IMHO. There are quite a few SPV (1) client implementations that remove the need to have all the blockchain stored locally. The things are moving even further in these field with the implementation of the payment protocol (2)
(1) http://bitcoin.stackexchange.com/questions/4649/what-is-an-s... (2) https://github.com/bitcoin/bips/blob/master/bip-0070.mediawi...
I'm particularly interested in their "intrinsic on line nature", care to elaborate a little bit further?
For more info see:
https://en.bitcoin.it/wiki/Transaction_fees
A 0 fee tx
http://blockexplorer.com/block/000000000002e0d610f875f5aa4fb...
- http://adpgtech.blogspot.it/2013/04/linuxzfs-is-great.html
- http://wiki.postgresql.org/images/8/86/PostgreSQL_on_ZFS.pdf
- http://lanyrd.com/2013/linuxcon-north-america/scqmfb/
- http://www.postgresql.org/message-id/CAGa5y0NkVLTNGywmZ6YS8O...