Hi, I believe this has been fixed on this commit 3dfa02a90bfa5202c305187cf90baea1b46f6240.
Could you try it once, with the latest master branch. Dinesh -- *Dinesh Kumar* Software Engineer Ph: +918087463317 Skype ID: dinesh.kumar432 www.enterprisedb.co <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/> *Follow us on Twitter* @EnterpriseDB Visit EnterpriseDB for tutorials, webinars, whitepapers<http://www.enterprisedb.com/resources-community> and more <http://www.enterprisedb.com/resources-community> On Thu, Nov 14, 2013 at 5:26 PM, Vik Fearing <vik.fear...@dalibo.com> wrote: > If a role does not have any expiration set, then just opening (and > validating) the role properties dialog will give it one. > > platform: Debian wheezy > language: English > Distribution: PGDG Apt > Version: 1.18.1 > > I think it's due to commit bb082def2452e085e27b8f356f6f13318912819e but > since I didn't set up a build environment, I can't say for sure. > > -- > Vik > > > > -- > Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-support >
