gistfile1.txt

LOG:  server process (PID 19793) was terminated by signal 9: Killed
DETAIL:  Failed process was running: CREATE INDEX i_l_orderkey_quantity ON lineitem (l_orderkey, l_quantity);
LOG:  terminating any other active server processes
connection to server was lost
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
connection to server was lost
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
connection to server was lost
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
connection to server was lost
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
connection to server was lost
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
connection to server was lost
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
connection to server was lost
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
connection to server was lost
LOG:  all server processes terminated; reinitializing

checkpoint_timeout = 600s
work_mem = 12GB                      #2 to 16GB
effective_cache_size = 192GB        #3/4 of total RAM (192GB)
default_statistics_target = 5000    #requires analyze to take effect
maintenance_work_mem = 32MB

server signaled
LOG:  received SIGHUP, reloading configuration files
never
Running vacuum freeze analyze...
LOG:  database system was interrupted; last known up at 2014-04-14 00:18:44 UTC
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  parameter "shared_buffers" cannot be changed without restarting the server
LOG:  parameter "checkpoint_timeout" changed to "600s"
LOG:  parameter "work_mem" changed to "12GB"
LOG:  parameter "effective_cache_size" changed to "192GB"
LOG:  parameter "default_statistics_target" changed to "5000"
LOG:  parameter "maintenance_work_mem" changed to "32MB"
LOG:  configuration file "/AXLE/postgres/pgdata1GB/postgresql.conf" contains errors; unaffected changes were applied
FATAL:  the database system is in recovery mode
psql: FATAL:  the database system is in recovery mode
FATAL:  the database system is in recovery mode
psql: FATAL:  the database system is in recovery mode
Checkpointing...
LOG:  redo starts at 0/178AA40
FATAL:  the database system is in recovery mode
psql: FATAL:  the database system is in recovery mode
Elapsed time: 0:07:46
Cleaning up before exiting
LOG:  received fast shutdown request
waiting for server to shut down....LOG:  abnormal database system shutdown
 done
server stopped


postgres@precise64:~/pg-tpch$ ./tpch_prepare 
Waiting for the Postgres server to start
FATAL:  could not map anonymous shared memory: Cannot allocate memory
HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 35188326400 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
Waiting for the Postgres server to start
Waiting for the Postgres server to start
Waiting for the Postgres server to start
Waiting for the Postgres server to start
^CCleaning up before exiting
/home/postgres/pg-tpch/pgtpch_defaults: line 31: kill: (19979) - No such process
/home/postgres/pg-tpch/pgtpch_defaults: line 33: kill: (19979) - No such process