On Wed, Nov 23, 2011 at 10:36 PM, Pongrácz István <[email protected]> wrote: > ----------------eredeti üzenet----------------- > Feladó: "Chris Travers" [email protected] > Címzett: [email protected] > Dátum: Wed, 23 Nov 2011 14:54:40 -0800 > ------------------------------------------------- > > >> The above messages tell me PostgreSQL is refusing to authenticate the >> user here. There is really very little room for the upgrade script to >> cause an issue like this. Is it possible the passwords expired? You > > Hello Chris, > > This can be the reason, I used the initial password, I did not care about the > expiring warning. > I create a new database to check this theory. > > At this point a have to say, this is a PEBCAK.
Well, it's probably better just to set the expiration: ALTER USER 'username' with valid until '2012-01-01'; Or something like that Best Wishes, Chris Travers ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Ledger-smb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
