BowerStudios.com

Link is a little older, but looks interesting: From enterprisedb.com

Postgres stores time in UTC, if you want to see the value of a date for a particular timezone, use one of the following:

SELECT now() AT TIME ZONE current_setting('TimeZone');
SELECT now() AT TIME ZONE 'EST5EDT';
SELECT now() AT TIME ZONE 'UTC';

From David Larochelle's blog

You can use:
COPY TABLE_NAME TO STDOUT WITH CSV HEADER
to push the output to a csv file.

thatJeffSmith.com

First we need to find out what cluster we're working with:
$ pg_lsclusters
Result:
Ver Cluster Port Status Owner Data directory Log file
9.3 main 5432 online postgres /var/lib/postgresql/9.3/main /var/log/postgresql/postgresql-9.3-main.log
Now, reload it using the version and cluster name
$ sudo pg_ctlcluster 9.3 main reload

1. First, add the Postgres driver to Oracle Sql Developer:

   Tools > Preferences > Database > "Third Party JDBC Drivers" > Add Entry

   Navigate to a save location of the Postgresql JDBC driver from jdbc.postgresql.org

2. Next, In Oracle Sql Developer, crate a new connection. Give it a Connection Name, Username, HostName, and Port. Now Save.
3. Exit Sql Developer
4. Open ~/.sqldeveloper/system4.0.3.16.84/o.jdeveloper.db.connection.12.1.3.2.41.140908.1359/connections.xml
5. Update the customUrl for the connection you just created to something like:

   <StringRefAddr addrType="customUrl">
   <Contents>jdbc:postgresql://localhost:5432/mydatabasename?ssl=true</Contents>
   </StringRefAddr>

   Basically, we're adding the ?ssl=true parameter to the connection string.

You can direct a statement to output to a file, with "\o"

Example from stackoverflow.com
db=>\o out.txt
db=>select * from mytable;

DbForge looks like a nice candidate, though it is only available in windows

From the Postgresql docs, use the alter role statement.

I'm reposting my edit to Ahmad Abuhasna's answer to my question here as the edit was rejected by the mods, but I think it is necessary to more directly expose the answer to the question. Thanks to Ahmad for pointing me in the right direction.

You could try enabling the log table for general queries.

The general_log table should already be present in the mysql schema with the following DDL:
CREATE TABLE `general_log` (
`event_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
ON UPDATE CURRENT_TIMESTAMP,
`user_host` mediumtext NOT NULL,
`thread_id` bigint(21) unsigned NOT NULL,
`server_id` int(10) unsigned NOT NULL,
`command_type` varchar(64) NOT NULL,
`argument` mediumtext NOT NULL
) ENGINE=CSV DEFAULT CHARSET=utf8 COMMENT='General log'

To enable the log:
SET global general_log = 1;

To send the log output to the table in the mysql schema rather than the default file location:
SET global log_output = 'table';

You can then simply query the log with:
select * from mysql.general_log;

Or to directly address the question specified on StackOverflow:
select argument, count(*) from mysql.general_log group by argument order by count(*) desc;
This query nicely groups select statements since we can't filter the query parameters out:
select LEFT(argument, INSTR(argument, 'where')), count(*)
from mysql.general_log
where argument not like 'update%'
group by LEFT(argument, INSTR(argument, 'where')) order by count(*) desc;

After running your queries that you want to investigate, running the following will turn off the log and avoid cluttering it with your investigative sql.
SET global general_log = 0;

Note: You won't want to run this in production as it does generate some overhead.

References from the mysql 5.5 docs:

• http://dev.mysql.com/doc/refman/5.5/en/query-log.html
• http://dev.mysql.com/doc/refman/5.5/en/log-destinations.html