Glad to know your problem was solved :-)
Goutham Naval wrote:
Hi Rommel,
Thank you very much for your help. As a windows admin, I deleted the
old postgres user account, and uninstalled postgresql and installed it
to get past the issue.
Kind Regards,
Gotham.
Date: Mon
Hi,
This happened to me before and the problem was with the 'postgres'
Windows account that was created during the first install. If you don't
specify a password for this account, the installer will choose a very
hard to guess, hard to remember password :-). I logged in as an
administrator and
ones I use most begin with "uuid_generate". I can
call these functions from within my own stored procs.
Rommel the iCeMAn
Barbados, Caribbean.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
> Can't help you with that, you'll need to report that on the pgadmin
> mailing list.
Will do.
> Did you remove the comment marker (#) from the timezone setting line?
Yes I did, which is why it baffles me. Here's what that part of my conf file
looks like:
# - Locale and Formatting -
datestyle
Hi List,
I'm experiencing strange behavior in pgAdmin. I recently noticed that my
PostgreSQL reports a different time to the OS. I checked the time zone
setting and realized it was set to 'Canada/Atlantic'. I tried using
pgAdmin's Backend Configuration Editor to change the time zone in
postgresql.
