I read up about msysconf in the Access help files - you're right, that's
normal behavior. I also read up on log settings in the PostgreSQL on-line
manual (very helpful). I have tried making the connection while upping the
debug level in between tries and I came up with this on levels 3 and 5 (but
not 4 ?!?):
010821.21:21:08.905 [2795] ERROR: job: Permission denied.
010821.21:21:08.905 [2795] NOTICE: LockReleaseAll: xid table corrupted
Does anyone know what the "LockReleaseAll: xid table corrupted" line means?
At 12:38 AM 8/22/01 +0300, you wrote:
>Logic would say, if you haven't changed anything then there's know reason
>why the behavior should change. I don't know why PG would be rejecting
>connections as the superuser, other than if you (ie, Access) is not
>actually connecting as the superuser. It looks like you're running PG
>7.1.x.. try enabling connection logging, just to make sure. As for
>MSysConf, that is something Access looks for to control things like
>background population and password caching. Notice that Access only looks
>for it once per connection. Have a look in Access help, I think the table
>definition and record meanings are in there. Also, you should read this
>FAQ:
> http://www.scw.org/pgaccess
>
>-Cedar
