On Sat, Mar 22, 2008 at 3:26 PM, <[EMAIL PROTECTED]> wrote: > All, > > I've just started seeing a strange error message in pgadmin3-1.8.2 on a > FreeBSD-6.3P1 system. I've just upgraded to pg-8.3.1 using ports. In the > SQL window any query gives me a pop-up saying : > > An error has occurred: > > Cannot get priority range for scheduling policy3. > > > If I hit the OK button the query runs fine and displays the result set > normally. What's going on here? Is this related to 8.3's tightening of > casting?
That doesn't sound like any PostgreSQL error message I can recall (and assuming you copied it verbatim, doesn't follow the PostgreSQL message style guide anyway). I'd try asking on one of the PostgreSQL lists - perhaps one of the hackers will have an idea where it's coming from (oh, and I don't think it's cast related). -- Dave Page EnterpriseDB UK Ltd: http://www.enterprisedb.com PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
