It looks like you are

designer2handbags — Mon, 28 Jun 2010 09:00:59 +0000

It looks like you are restarting the DB service every time you toggle logging. Is there a way to do that without a restart?

I needed a quick way to

stephan90 — Sat, 08 Aug 2009 05:58:18 +0000

I needed a quick way to debug what PDO statements were being executed (and their parameters) by Drupal 7's DBTNG. I could have used the devel module, ...

A lot of useful information

who-when-how — Sat, 08 Aug 2009 04:25:57 +0000

A lot of useful information in this post, thanks. I feel that it might even be too much for me to “digest” .

Testing and debugging SQL

stephan90 — Tue, 04 Aug 2009 05:53:47 +0000

Testing and debugging SQL database-methods. After an SQL Database Method has been created.

Well, the spam - "let me get

Greg K — Wed, 29 Jul 2009 12:56:42 +0000

Well, the spam - "let me get my link listed post" was actually useful. I missed this thread when it was active. (for regular users, the post has been unpublished)

I am going to look around to see if there is a way to do this run time as well for mySQL as that would be nice. With our new CMS we launched at the beginning of the year, we are doing pretty much all PDO, called from within data classes, and being able to check the actual query would be nice. However full time logging with 20+ active cevelopment sites would fill the logs quickly.

Thanks for the tips Jeeves!

-Greg

JeevesBond wrote: My

Abhishek Reddy — Thu, 09 Jul 2009 06:22:40 +0000

JeevesBond wrote:

My methodology was to vim /etc/init.d/postgresql-8.3, see what the init script was using to control the service, then do man pg_cluster. After a bit of rooting around in man files I found the startup options for debugging.

Fair enough. Rather new to Postgres myself, and I had resorted to restarting the service whilst updating postgresql.conf, when I had to deploy it for the first time in anger. Have been getting used to psql since then, however.

Interesting thread, thanks for posting it.

Have you always used that

JeevesBond — Thu, 09 Jul 2009 03:56:00 +0000

Have you always used that RDBMS? If not, what made you abandon MySQL?

I haven't really abandoned MySQL, but I do think of it as being a little like the Internet Explorer of the RDBMS world.

I use Postgres mostly for Drupal development, both because the community needs testing using it and due to its closer adherence to the SQL standards. Closer adherence to the standards means I write better -- or at least more portable -- code.

MySQL 5.1 allows you to toggle logging during runtime.

That's interesting, I was trying to get this working using mysqladmin without much luck. Think it may have been pesky Apparmour disallowing MySQL access to a log file. I'll try it again.

*** EDIT ***
Seems 5.1 is when general_log was introduced. Am on 5.0.75 here, that's why it doesn't work.

There's the log variable, but that's read-only at runtime. So, to clarify are you MySQL 5.1+ people doing the following to turn on logging?

mysql -uroot -p
SET general_log = ON;

Am I missing something,

JeevesBond — Thu, 09 Jul 2009 03:49:56 +0000

Am I missing something, Jeeves?

Nope, that's a really good idea actually.

I've only ever used psql for creating users, databases and fiddling with permissions. It never even occured to me that I could change the logging settings at runtime!

So, as you can see, I was assuming I'd have to restart the daemon to get debugging.

Instructions for MySQL: Copy

JeevesBond — Thu, 09 Jul 2009 03:38:04 +0000

Instructions for MySQL:

Copy and paste the following to the command line:

sudo /etc/init.d/mysql stop

Then:

sudo mysqld --log=/var/log/mysql.log &

Will start up a copy of MySQL that logs all queries to the /var/log/mysql.log file.

Now, to view the queries as they're being run, copy and paste this to the command line:

tail -f /var/log/mysql.log

teammatt3 wrote: It looks

Abhishek Reddy — Wed, 08 Jul 2009 23:34:00 +0000

teammatt3 wrote:

It looks like you are restarting the DB service every time you toggle logging. Is there a way to do that without a restart?

Good point. I see no reason why the logging configuration settings cannot be updated at runtime.

You ought to be able to drop into psql as the postgres superuser and do something like this:

# sudo -u postgres psql
postgres=# set log_min_messages to DEBUG2;

Am I missing something, Jeeves?