From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Scott Holmes <sholmes(at)pacificnet(dot)net> |
Cc: | PG-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Users in pg_shadow |
Date: | 2001-03-01 19:08:34 |
Message-ID: | Pine.LNX.4.30.0103012006200.760-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Scott Holmes writes:
> I have a cron script set up to run VACUUM ANALYZE on two databases that appear
> to work fine except for a couple of messages that show up in the log:
>
> FATAL 1: SetUserId: user 'newsltr' is not in 'pg_shadow'
> FATAL 1: SetUserId: user 'wcgc_pg' is not in 'pg_shadow'
>
> newsltr and wcgc_pg are the respective names of the databases, there are no
> users with these names. This is on a postgresql-7.0.2 running on a Red Hat 6.2
You should make your cron script to connect as the proper user, probably
using the -U option of psql or vacuumdb. Otherwise the user name defaults
to one of various things, which is probably not desired here.
> I've seen no problems resulting from this but I would like to understand why.
Only if the fact that the VACUUM ANALYZE probably didn't actually execute
is not a problem... ;-)
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
From | Date | Subject | |
---|---|---|---|
Next Message | Denis Perchine | 2001-03-01 19:12:33 | Re: Postgres eats up memory when using cursors |
Previous Message | Tom Lane | 2001-03-01 19:07:05 | Re: Postgres eats up memory when using cursors |