[quote]I didn't know that the Pentium FP bug was a software bug.[/quote] Indeed it was. Microcode in the CPU is software just as much as the assemby used for your Bios is software or the embedded code running in the microcontroller of your microwave is software.
Full text searching has existed for a number of years and is actively used by a few Russian search engines on large volumes of content (millions of text documents), among other places.
Take a peak in the contrib directory of the source tree for tsearch.
One major benefit to doing these kinds of strange things is tracking down bugs.
Long standing but seldomly seen bugs (hard to solve what you cannot repeat) can become repeatable and very visible in different combinations of software or hardware.
Different CPUs or architecture, different compilers and different kernels will all tickle and expose userland bugs.
It is probably simpler than that. Google may currently license several hundred copies of MS Office for their employees desktops or use OpenOffice on employee desktops. Hiring 2 people for a couple of years for a product that is more tailored to their way of doing things is probably more effective than continuing to purchase MS Office or purchase high end hardware.
A 10 minute time savings per employee per day may add up to several times what they'll spend on development -- especially if it is time saved by senior management.
Now, just maybe, the presence of these weapons can be called a deterant, so its possible that possessing them is a necessary evil. However, to be quite honest, if we ever "need" them -- I really do hope they fail to work. You don't even need to possess the weapons for them to be a deterrant.
Canada has the parts and expertise required to build bombs and a delivery system within about 3 months. Heck, they used to sell the US weapons grade plutonium and many of the designers of various rockets came from the Avro Arrow team after leaving for various US firms.
3 months is plenty of time to notice that something is going very wrong in world politics.
For this reason Canada is considered to be armed country despite not having a single Nuclear WMD.
Canada is in the same boat with biological weapons. All the parts and expertise including the research labs and viral strains necessary but their military has not bothered to actually build one in a while.
The labels were removed when the design was commoditized by knock-offs which flooded the market.
The original product is the Homan and the most popular knock-off is Human. You might have difficulty seeing the difference in the label but there is a huge price and quality difference.
Technically PostgreSQL 8.1 can merge two scans of single column indexes together into a single table scan. This falls somewhere between a bitmap and regular indexing -- it builds a lossy bitmap on the fly to do all of the inter-column tricks.
With the beta's I've been taking my multi-column indexes and splitting them up to let the bitmap Index Scan deal with them instead.
[quote]And no 64-bit version (though I've read a few people have managed to compile one, I wouldn't trust it unless Postgres gave it the thumbs up).[/quote]
I see you have never used PostgreSQL. You might want to try sometime. I stopped reading at this point.
SCREW THE FISH! I would rather see one HUMAN saved and see ALL the marine life in the world wiped out than one HUMAN killed to save all the marine life.
Your solution is akin to hitting New York with a nuclear bomb to prevent New York from being hit with a terrorist attack. Wipe out all marine life and far more than one human will die as a result.
Now we take the argument into grey area of X humans die for Y %age of marine life. Is X larger than 0 for very small values of Y and does this device cause more damage than Y?
It gets funny when you try to measure this stuff. Consider that public health care in the East Coast provinces of Canada has degraded as an indirect result of over-fishing (lost income in the region from lack of fish).
I would rather see a human killed who volunteered to be in a situation where that was a possibility than a human killed who is an innocent bystander. Now, how the heck do we determine if it would or would not indirectly harm an innocent human.
That seems awfully nitpicky compared to supporting transactions and referential integrity constraints, but MySQL 5 supports the sort of strict date checking you're asking for as well.
For my own usage, any flaw which can cause data loss is equally as bad as any other. Nitpicky is exactly right. Bugs are one thing as they will eventually be discovered and quashed, but a feature designed (or mis-designed) with dataloss potential is reflective of the programmer and vendor priorities -- they don't care about my data only that there is a product on the shelves.
ACID is more than just the transaction. Lets look at C:
Consistency states that only valid data will be written to the database. If, for some reason, a transaction is executed that violates the database's consistency rules, the entire transaction will be rolled back and the database will be restored to a state consistent with those rules.
Now, take a peak at MySQLs datetime handling regarding dates such as 2005-02-29. I'll admit I haven't checked recently but does it still round down integers are are too large as well? It should reject the data completely and not massage it into place.
With feature creep being what it is, crappy website databases all of a sudden become important and store customer information. I simply don't trust MySQL.
You can be truly happy without being fully happy. I am truly happy about many things in life. But I'm not fully happy, as there are aspects of my life (as with everyone else) that are not perfect. You had better hope you are happy that you are a perfectionist.
Nothing is worse than a perfectionist purposfully making mistakes in an attempt to be less perfect because less than perfect is better than perfect.
Smush? Smush? Are you crazy? Do you know what kind of a radar signature a smushed tinfoil hat has? They'll see you from miles away!
A properly made tinfoil hat will bounce the brainscanning waves (and radar waves) at odd angles which would not send the signal back to the sender. Nice clean folds. They chould be straight enough that the foil does not touch the head in all locations.
Mouse geastures work for browsers, so how about tongue gestures? Have a small sensor that detects motion and require moving the tongue in some pattern to activate and deactivate.
My favorite comment though was the PDF- a document that can be read on any PC. Oh yeah? Can it be read on the PC that doesn't have a PDF reader on it? Hmm! Yes, it can often be read on PCs without PDF readers. Strings is your friend.
The earth is NOT fragile. Humans are fragile though. Nobody really cares about what the earth will become outside of how it impacts us.
Whether human created or not, we're going to have to make a serious investment in relocation soon. The price tag tied to Katrina was high, but just wait until we get to move New York, Miami and other coastal cities.
Slashdot Mirror
[quote]I didn't know that the Pentium FP bug was a software bug.[/quote]
Indeed it was. Microcode in the CPU is software just as much as the assemby used for your Bios is software or the embedded code running in the microcontroller of your microwave is software.
Full text searching has existed for a number of years and is actively used by a few Russian search engines on large volumes of content (millions of text documents), among other places.
Take a peak in the contrib directory of the source tree for tsearch.
Documentation for TSearch
You used to do it using a short statement timeout.
set statement_timeout = 200; -- 200ms
SELECT * FROM UPDATE; -- Waits at most 200ms
Catch the exception indicating the query was cancelled (row locked) or continue.
Not the greatest but it has worked well enough for me with a few hundred automated processes pulling things out of a queue several times per second.
One major benefit to doing these kinds of strange things is tracking down bugs.
Long standing but seldomly seen bugs (hard to solve what you cannot repeat) can become repeatable and very visible in different combinations of software or hardware.
Different CPUs or architecture, different compilers and different kernels will all tickle and expose userland bugs.
It is probably simpler than that. Google may currently license several hundred copies of MS Office for their employees desktops or use OpenOffice on employee desktops. Hiring 2 people for a couple of years for a product that is more tailored to their way of doing things is probably more effective than continuing to purchase MS Office or purchase high end hardware.
A 10 minute time savings per employee per day may add up to several times what they'll spend on development -- especially if it is time saved by senior management.
Now, just maybe, the presence of these weapons can be called a deterant, so its possible that possessing them is a necessary evil. However, to be quite honest, if we ever "need" them -- I really do hope they fail to work.
You don't even need to possess the weapons for them to be a deterrant.
Canada has the parts and expertise required to build bombs and a delivery system within about 3 months. Heck, they used to sell the US weapons grade plutonium and many of the designers of various rockets came from the Avro Arrow team after leaving for various US firms.
3 months is plenty of time to notice that something is going very wrong in world politics.
For this reason Canada is considered to be armed country despite not having a single Nuclear WMD.
Canada is in the same boat with biological weapons. All the parts and expertise including the research labs and viral strains necessary but their military has not bothered to actually build one in a while.
The labels were removed when the design was commoditized by knock-offs which flooded the market.
The original product is the Homan and the most popular knock-off is Human. You might have difficulty seeing the difference in the label but there is a huge price and quality difference.
Technically PostgreSQL 8.1 can merge two scans of single column indexes together into a single table scan. This falls somewhere between a bitmap and regular indexing -- it builds a lossy bitmap on the fly to do all of the inter-column tricks.
With the beta's I've been taking my multi-column indexes and splitting them up to let the bitmap Index Scan deal with them instead.
Never trust a journalist to get ... facts straight.
There. Fixed it for you.
This can freeze your browser.
It's as bad as Google Maps with far too many location tags and polygons.
They've had official support for 64 bit platforms for at least 5 years.
[quote]And no 64-bit version (though I've read a few people have managed to compile one, I wouldn't trust it unless Postgres gave it the thumbs up).[/quote]
I see you have never used PostgreSQL. You might want to try sometime. I stopped reading at this point.
SCREW THE FISH! I would rather see one HUMAN saved and see ALL the marine life in the world wiped out than one HUMAN killed to save all the marine life.
Your solution is akin to hitting New York with a nuclear bomb to prevent New York from being hit with a terrorist attack. Wipe out all marine life and far more than one human will die as a result.
Now we take the argument into grey area of X humans die for Y %age of marine life. Is X larger than 0 for very small values of Y and does this device cause more damage than Y?
It gets funny when you try to measure this stuff. Consider that public health care in the East Coast provinces of Canada has degraded as an indirect result of over-fishing (lost income in the region from lack of fish).
I would rather see a human killed who volunteered to be in a situation where that was a possibility than a human killed who is an innocent bystander. Now, how the heck do we determine if it would or would not indirectly harm an innocent human.
Perhaps he was thinking that gamers are the kids and consumers are their parents?
It doesn't fit with the people I know who have purchased the console, but oh well.
That seems awfully nitpicky compared to supporting transactions and referential integrity constraints, but MySQL 5 supports the sort of strict date checking you're asking for as well.
For my own usage, any flaw which can cause data loss is equally as bad as any other. Nitpicky is exactly right. Bugs are one thing as they will eventually be discovered and quashed, but a feature designed (or mis-designed) with dataloss potential is reflective of the programmer and vendor priorities -- they don't care about my data only that there is a product on the shelves.
ACID is more than just the transaction. Lets look at C:
Consistency states that only valid data will be written to the database. If, for some reason, a transaction is executed that violates the database's consistency rules, the entire transaction will be rolled back and the database will be restored to a state consistent with those rules.
Now, take a peak at MySQLs datetime handling regarding dates such as 2005-02-29. I'll admit I haven't checked recently but does it still round down integers are are too large as well? It should reject the data completely and not massage it into place.
With feature creep being what it is, crappy website databases all of a sudden become important and store customer information. I simply don't trust MySQL.
I couldn't argee more.
My spelling and grammer mistakes are natural incompetence!
Indeed. a 2" by 3" screen could still be 1600 x 1200 pixels which would maintain most of the detail -- they're just tiny pixels.
You can be truly happy without being fully happy. I am truly happy about many things in life. But I'm not fully happy, as there are aspects of my life (as with everyone else) that are not perfect.
You had better hope you are happy that you are a perfectionist.
Nothing is worse than a perfectionist purposfully making mistakes in an attempt to be less perfect because less than perfect is better than perfect.
Smush? Smush? Are you crazy? Do you know what kind of a radar signature a smushed tinfoil hat has? They'll see you from miles away!
A properly made tinfoil hat will bounce the brainscanning waves (and radar waves) at odd angles which would not send the signal back to the sender. Nice clean folds. They chould be straight enough that the foil does not touch the head in all locations.
regards,
Agent Watson
BSD (Brain Scan Department)
Mouse geastures work for browsers, so how about tongue gestures? Have a small sensor that detects motion and require moving the tongue in some pattern to activate and deactivate.
My favorite comment though was the PDF- a document that can be read on any PC. Oh yeah? Can it be read on the PC that doesn't have a PDF reader on it? Hmm!
Yes, it can often be read on PCs without PDF readers. Strings is your friend.
4. Watch as theives take your computer because you forgot to close the safe door.
The earth is NOT fragile.
Humans are fragile though. Nobody really cares about what the earth will become outside of how it impacts us.
Whether human created or not, we're going to have to make a serious investment in relocation soon. The price tag tied to Katrina was high, but just wait until we get to move New York, Miami and other coastal cities.
Canadians won't be there but we might have Canadarm 3 on location for remote hand shaking.