ALTER TABLE foo ORDER BY something;
does what OPTIMIZE does (but in a totally different way), plus clusters data based on the ORDER BY. In a few cases, this can be quite beneficial. Here’s an example:
* Table is bigger than will fit in cache.
* Table has two ways to look at it, one is date oriented, the other is by some “key”.
* There are hundreds of rows for each key (one per day)
* There are thousands of keys for each day.
* Data is coming in daily — That is, new rows are appended to the table and/or filling in holes left by deleted rows.
* Your main query is SELECT … WHERE key = ‘…’ — that is, one row per day.

Normally the rows for that SELECT will be quite scattered, and because of the size of the table, it will take a lot of disk hits.

The ALTER table will rearrange the rows so that the SELECT will find all the rows for the ‘key’ clustered in a few blocks, hence much less disk I/O.

IF this use of ALTER feels right for you, I recommend doing it monthly. Watch out: It could take hours (remember, it is bigger than will fit in cache).

For small tables (say, <100K rows), the ALTER is reasonably fast, but gives only limited improvement.

I have felt the need for the ALTER in less than 1% of the tables I have studied.

-bash-3.1$ pg_ctl stop
waiting for server to shut down……………………………………………………… failed
pg_ctl: server does not shut down

Sometimes postgres does not want to shutdown by just issuing a pg_ctl stop as the postgres user. User might feel the need to “kill -9″ the postgres processes however this could be dangerous for PostgreSQL. Instead of trying to kill the PID follow the directions below in an attempt to stop postgres in an organized fashion.

1. Attempt Normal Stop: bash-3.1$pg_ctl stop
2. Attempt Smart Stop: bash-3.1$pg_ctl stop -m s
3. Attempt Fast Stop: bash-3.1$pg_ctl stop -m f
4. Attempt Immediate Stop: bash-3.1$pg_ctl stop -m i
The immediate stop almost always ends up stopping postgres if you are having trouble in stopping the processes. If the immediate stop does not work the issue should be investigated before attempting to kill -9 the PID.

Try this:

find . -name ‘*’ -exec rm {} \;

What to force it so it does not ask you y/n for each file?

find . -name ‘*’ -exec rm -f {} \;

To remove/delete only directories just add a ‘type’ flag to find…

find . -name ‘*’ -type d -exec rm {} \;

First:
sudo apt-get install linux-image-

This will give you all current options for a new linux kernel image.

Next do the same with the headers!
sudo apt-get install linux-headers-

Make sure you do your headers too!!!

find -type f -name ‘*.rar’ -exec unrar -pPASSWORD x {} \;