"Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
> I just tested this by artificially creating a user with duplicate usesysid
> (I had to UPDATE pg_shadow to do it : the CREATE USER command is guarded
> against this) and got exactly the symptoms you report:
FWIW, this sort of problem should be imp
On Thu, Dec 06, 2001 at 01:32:56PM -0500, Yanek Korff wrote:
> > Here's your problem: user1 has the same userid as pgsql. this
> > used to happen in 7.0, I think. Is that what you're running?
> I'm sure it's what I used to be running. I am running this now:
> postgresql-7.1.2_2
> according to Fr
> Here's your problem: user1 has the same userid as pgsql. this
> used to happen in 7.0, I think. Is that what you're running?
I'm sure it's what I used to be running. I am running this now:
postgresql-7.1.2_2
according to FreeBSD ports.
> As to fixing it - have you created a lot of db objects
On Wed, 5 Dec 2001, Yanek Korff wrote:
> here's pg_user:
> usename | usesysid | usecreatedb | usetrace | usesuper | usecatupd |
> passwd | valuntil
> +--+-+--+--+---+
> --+--
> pgsql | 72 | t | t
Well, a while ago I set up postgresql and have been using it for a small
database ever since. I'm now looking at local authentication and
permissions and a number of questions have come up. When I run select *
from pg_database, I get this:
datname | datdba | encoding | datistemplate |
