I just queried my database with millions of customers in the USA. The maximum first name length was 46. I go with 50. (Of course, only 500 of those were over 25, and they were all cases where data imports resulted in extra junk winding up in that field.) Last name was similar to first … Read more
Either connect to node instance and use shutdown command or if you are on ubuntu you can try to restart redis server through init.d: /etc/init.d/redis-server restart or stop/start it: /etc/init.d/redis-server stop /etc/init.d/redis-server start On Mac redis-cli shutdown
I’m the CTO of 10gen (developers of MongoDB) so I’m a bit biased, but I also manage a few sites that are using MongoDB in production. businessinsider has been using mongo in production for over a year now. They are using it for everything from users and blog posts, to every image on the site. … Read more
The basic idea is that you have two numbers to make up a primary key- a “high” number and a “low” number. A client can basically increment the “high” sequence, knowing that it can then safely generate keys from the entire range of the previous “high” value with the variety of “low” values. For instance, … Read more
You can use pg_terminate_backend() to kill a connection. You have to be superuser to use this function. This works on all operating systems the same. SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE — don’t kill my own connection! pid <> pg_backend_pid() — don’t kill the connections to other databases AND datname=”database_name” ; Before executing this query, you … Read more
You are correct that storing the password in a plain-text field is a horrible idea. However, as far as location goes, for most of the cases you’re going to encounter (and I honestly can’t think of any counter-examples) storing the representation of a password in the database is the proper thing to do. By representation … Read more
1. Not using appropriate indices This is a relatively easy one but still it happens all the time. Foreign keys should have indexes on them. If you’re using a field in a WHERE you should (probably) have an index on it. Such indexes should often cover multiple columns based on the queries you need to … Read more
You don’t need to create an intermediate file. You can do pg_dump -C -h localhost -U localuser dbname | psql -h remotehost -U remoteuser dbname or pg_dump -C -h remotehost -U remoteuser dbname | psql -h localhost -U localuser dbname using psql or pg_dump to connect to a remote host. With a big database or … Read more
I think lucene syntax is supported so: http://localhost:9200/foo/_search?pretty=true&q=*:* size defaults to 10, so you may also need &size=BIGNUMBER to get more than 10 items. (where BIGNUMBER equals a number you believe is bigger than your dataset) BUT, elasticsearch documentation suggests for large result sets, using the scan search type. EG: curl -XGET ‘localhost:9200/foo/_search?search_type=scan&scroll=10m&size=50’ -d ‘ … Read more
Must read Get your database under version control. Check the series of posts by K. Scott Allen. When it comes to version control, the database is often a second or even third-class citizen. From what I’ve seen, teams that would never think of writing code without version control in a million years– and rightly so– … Read more