What is in the PostgreSQL_Server_Services.log File and How do I Shrink it?

Thanks for the response. I mistyped in the question as I understood it was a log file. The DB itself is only about 1-2GB. As for reviewing I am fine with modifying the permissions and examining the file in the console or other app but I am most interested in how to manage it safely. Can I just clear the log contents? If so what is the safe way to do so? I know with many DB's the log file is critical to it's function and if things happen to the log file it can render the DB unusable. In addition what is the best way to modify the rotation routine it uses and set the logging level? (I have pasted the .plist contents for Postgresql for Server Services below)

I have also downloaded and installed pgAdmin but have not gone through the steps of connecting it to the DB and log file (users setup etc.)

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>ProgramArguments</key>

<array>

<string>-D</string>

<string>/Library/Server/PostgreSQL For Server Services/Data</string>

<string>-c</string>

<string>unix_socket_directory=/Library/Server/PostgreSQL For Server Services/Socket</string>

<string>-c</string>

<string>logging_collector=on</string>

<string>-c</string>

<string>log_connections=on</string>

<string>-c</string>

<string>log_lock_waits=on</string>

<string>-c</string>

<string>log_statement=ddl</string>

<string>-c</string>

<string>log_line_prefix=%t </string>

<string>-c</string>

<string>listen_addresses=</string>

<string>-c</string>

<string>log_directory=/Library/Logs/PostgreSQL</string>

<string>-c</string>

<string>log_filename=PostgreSQL_Server_Services.log</string>

<string>-c</string>

<string>unix_socket_group=_postgres</string>

<string>-c</string>

<string>unix_socket_permissions=0770</string>

</array>

</dict>

</plist>

Oh here are some of the errors it has in the log file:

2013-09-23 13:18:23 EDT ERROR: role "collab" already exists

2013-09-23 13:18:23 EDT STATEMENT: CREATE ROLE collab SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN;

2013-09-23 13:18:23 EDT ERROR: role "webauth" already exists

2013-09-23 13:18:23 EDT STATEMENT: CREATE ROLE webauth SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN;

2013-09-23 13:18:23 EDT ERROR: database "collab" already exists

2013-09-23 13:18:23 EDT STATEMENT: CREATE DATABASE collab;

I also saw this further back in the logs... many times in a row

LOG: could not open log file "/Library/Logs/PostgreSQL/PostgreSQL_Server_Services.log": Too many open files

OK a little more info... I found the postgresql.conf file and some of the settings that I would think should be in effect are not and they are commented out instead. Does anybody recommend uncommenting the log rotation etc from below?

# These are only used if logging_collector is on:

#log_directory = 'pg_log' # directory where log files are written,

# can be absolute or relative to PGDATA

#log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,

# can include strftime() escapes

#log_file_mode = 0600 # creation mode for log files,

# begin with 0 to use octal notation

#log_truncate_on_rotation = off # If on, an existing log file with the

# same name as the new log file will be

# truncated rather than appended to.

# But such truncation only occurs on

# time-driven rotation, not on restarts

# or size-driven rotation. Default is

# off, meaning append to existing files

# in all cases.

#log_rotation_age = 1d # Automatic rotation of logfiles will

# happen after that time. 0 disables.

#log_rotation_size = 10MB # Automatic rotation of logfiles will

# happen after that much log output.

# 0 disables.

Well to add to this I have gone ahead and copied then deleted the old 188GB log. As soon as I moved it to the trash it created a new one. I rebooted and will monitor it's growth. I guess my only outstatnding issue is how to manage this in the future. Seems the OS should be doing some kind of truncation or rotation automatically as it does not offer direct maintenance out of the box to the Postgresql DB settings.

If anyone can tell me if modifying the conf file settings for the log would work (they are commented out now so I am not sure why it is logging anyways). My hunch is there is a way to modify the plist file to control things since as I noted the log settings in the conf file are commented out.

Thanks!