Re: Use of Serial Datatype and Sequence Issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Keary Suska <hierophant(at)pcisys(dot)net>
Cc: Mart=?ISO-8859-1?B?7W4gTWFycXXp?=s <martin(at)bugs(dot)unl(dot)edu(dot)ar>, pgsql-general(at)postgresql(dot)org
Subject: Re: Use of Serial Datatype and Sequence Issue
Date: 2001-11-06 21:09:57
Message-ID: 18236.1005080997@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgsql-general

Keary Suska <hierophant(at)pcisys(dot)net> writes:
> On a separate issue, in 7.0.3, the \connect lines would fail because the
> passwords for the root user and the database owner are different, so I would
> have to dump and reload as root user, otherwise the pg_class updates would
> fail. Has this been solved in 7.1.3?

I believe that 7.1 psql will prompt for passwords as necessary, so this
works, but it's awfully tedious. Better to arrange things so that you
don't need to give a password.

There is support in 7.2 (not sure if it was in 7.1) for the ownership
changes to be executed via "SET current_userid" style commands, so that
as long as you connect as superuser to start with (to be allowed to do
this SET) you shouldn't need to answer password prompts for individual
ownership changes. But in a pg_dumpall script you'll probably still
have to answer once per database ...

regards, tom lane

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Jean-Michel POURE 2001-11-07 14:30:00 Fwd: Re: [GENERAL] Howto change column length
Previous Message Keary Suska 2001-11-06 21:01:14 Re: Use of Serial Datatype and Sequence Issue

Browse pgsql-general by date

  From Date Subject
Next Message Culley Harrelson 2001-11-06 21:18:18 Re: functions vs embedded SQL
Previous Message Joshua Drake 2001-11-06 21:08:55 Re: Sourceforge moving from PostgreSQL to Oracle