PGError: ERROR: unrecognized time zone name: “UTC”?

Yeap, it may have seemed that there is something seriously broken with the database. I remembered installing PostgreSql via homebrew, but possibly not stopping the macport installation of the postgres server, that was still running in the background Through the assistance of another developer (RhodiumToad), I was able to fix this by doing the following steps: stop the server re-run initdb start the server again Earlier, I removed /usr/local/var/postgres, via rm -rf /usr/local/var/postgres. So this is what I needed to do: ps axw find the postgres server 117?

S 0:00.23 /usr/local/Cellar/postgresql/9.0.3/bin/postgres -D /usr/local/var/postgres -r /usr/local/var/postgres/server kill it, which should also kills any other postgres process' running in the bg kill 117 The above killed the process and also stopped the server. Now I had to initialize the database and everything seems to work correctly again: initdb /usr/local/var/postgres Hope this helps someone one who comes across the same issue.

Yeap, it may have seemed that there is something seriously broken with the database. I remembered installing PostgreSql via homebrew, but possibly not stopping the macport installation of the postgres server, that was still running in the background. Through the assistance of another developer (RhodiumToad), I was able to fix this by doing the following steps: stop the server re-run initdb start the server again Earlier, I removed /usr/local/var/postgres, via rm -rf /usr/local/var/postgres.So this is what I needed to do: ps axw find the postgres server 117?

S 0:00.23 /usr/local/Cellar/postgresql/9.0.3/bin/postgres -D /usr/local/var/postgres -r /usr/local/var/postgres/server. Kill it, which should also kills any other postgres process' running in the bg kill 117 The above killed the process and also stopped the server. Now I had to initialize the database and everything seems to work correctly again: initdb /usr/local/var/postgres Hope this helps someone one who comes across the same issue.

Not 100% sure but the way you define the scope makes a string out of the Time parameters you pass in, which may be causing some issues. Try using symbols instead and see if that works: scope { :conditions => {:created_at => 1.month.ago..Time. Now}, :order => 'model.

Created_at DESC' }.

Well, I'm guessing that something in that line in your model is making it try to fix down the time zone in use when talking to the database. I guess it makes a kind of sense... Anyway, assuming that the string SET time zone 'UTC' is the command being sent to postgresql on connection (which seems to be the case, looking at that backtrace) then I would expect it to work. Certainly it works on my own (Linux) installation of postgresql.

Can you verify that it fails if you connect to the database with psql and issue the command manually? It does seem to indicate a broken postgresql installation. Cleaning things away and reinstalling would be a reasonable step to try.My own installation of postgresql is using the timezone data from the operating system, i.e.

Looking in /usr/share/zoneinfo. It's possible that your installation is trying to pick up the data from some location that was present during build but has been removed since as you transitioned over. I believe it should be that it can't find a location with the data at configure time, it will install its own bundled copy.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.