Dear All,
I am in the process of upgrading an existing database from PostgreSQL 8.1 to
9.1 . In trial upgrades I have discovered that in 9.1 only superusers can
login to phpPgAdmin. The database has a number of users who are already
accustomed to using phpPgAdmin but for whom it would not be appro
johnkn63 wrote:
> I am in the process of upgrading an existing database from PostgreSQL
8.1 to
> 9.1 . In trial upgrades I have discovered that in 9.1 only superusers
can
> login to phpPgAdmin. The database has a number of users who are
already
> accustomed to using phpPgAdmin but for whom it would
The phpPgAdmin message is "login failed" if I change the same user to a
superuser they can login.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/non-superuser-login-phpPgAdmin-PostgreSQL-9-1-tp5723838p5723841.html
Sent from the PostgreSQL - admin mailing list archive a
Hi,
On Thu, 2012-09-13 at 01:30 -0700, johnkn63 wrote:
> The phpPgAdmin message is "login failed" if I change the same user to
> a superuser they can login.
Did you check pg_hba.conf? What's in the PostgreSQL logs?
Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://w
I have checked the pg_hba.conf the log says 'CST FATAL: password
authentication failed for user "test8"'.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/non-superuser-login-phpPgAdmin-PostgreSQL-9-1-tp5723838p5723843.html
Sent from the PostgreSQL - admin mailing li
johnkn63 wrote:
> I have checked the pg_hba.conf the log says 'CST FATAL: password
> authentication failed for user "test8"'.
That indicates a wrong password.
How does pg_hba.conf look?
Yours,
Laurenz Albe
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to
Thank you for your patience. Whilst this is the error one gets for a wrong
password, this is not the case here simply changing the status of the user
to superuser without touching the password allows the user to login,
removing superuser status the reverse.
This login error might be caused by th
johnkn63 wrote:
> Thank you for your patience. Whilst this is the error one gets for a
wrong
> password, this is not the case here simply changing the status of the
user
> to superuser without touching the password allows the user to login,
> removing superuser status the reverse.
>
> This login e
Hello all,
I get the following output from pg_upgrade when trying to upgrade a
test cluster on Windows 7 x64:
c:\Daten>path
PATH=c:\windows;c:\windows\system32;c:\Program Files\PostgreSQL\9.2\bin
c:\Daten>pg_upgrade --old-bindir="c:\Program Files\PostgreSQL\9.1\bin"
--new-bindir="c:\Program Fil
> That's if you started the server with -b.
now how do I find out how server is starting and how do I change it? I am
running 9.1 on debian
>Can you connect with
>"psql -h 127.0.0.1 -U nonsuperuser -d database" ?
no,
psql -h 127.0.0.1 -U nonsuperuser -d database
does not work
though o
johnkn63 wrote:
>> That's if you started the server with -b.
> now how do I find out how server is starting and how do I change it?
I am
> running 9.1 on debian
Look at the output of "pg_ctl status".
What do you see there?
Actually, the error message would be different in this case, so
I don't
[copying the list; please keep the list copied on all replies]
Ramana Panda wrote:
> I am using the Version : *"PostgreSQL 8.0.0 on i686-pc-mingw32,
> compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)"*
You didn't even keep up on bug fix releases? It's amazing that your
database is still r
On Thu, Sep 13, 2012 at 02:15:00PM +0200, Christian Ullrich wrote:
> Hello all,
>
> I get the following output from pg_upgrade when trying to upgrade a
> test cluster on Windows 7 x64:
>
> c:\Daten>path
> PATH=c:\windows;c:\windows\system32;c:\Program Files\PostgreSQL\9.2\bin
>
> c:\Daten>pg_upg
I tried - the results where as predicted whilst a non-superuser does not
work but once altered to superuser does work.
So what next?
Regards
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/non-superuser-login-phpPgAdmin-PostgreSQL-9-1-tp5723838p5723886.html
Sent
And pg_ctl status seems normal :-
/usr/lib/postgresql/9.1/bin/pg_ctl -D /var/lib/postgresql/9.1/main/
status
returns:-
pg_ctl: server is running (PID: 1040)
/usr/lib/postgresql/9.1/bin/postgres "-D" "/var/lib/postgresql/9.1/main"
"-c" "config_file=/etc/postgresql/9.1/main/postgresq
* Bruce Momjian wrote:
On Thu, Sep 13, 2012 at 02:15:00PM +0200, Christian Ullrich wrote:
c:\Daten>path
PATH=c:\windows;c:\windows\system32;c:\Program Files\PostgreSQL\9.2\bin
c:\Daten>pg_upgrade --old-bindir="c:\Program Files\PostgreSQL\9.1\bin"
--new-bindir="c:\Program Files\PostgreSQL\9.2
On Wed, Sep 12, 2012 at 10:13:38PM -0500, Kevin Grittner wrote:
> Radovan Jablonovsky wrote:
>
> > In documentation
> > http://www.postgresql.org/docs/9.1/static/routine-vacuuming.html
> > is this information about autovacuum_freeze_max_age: "if
> > autovacuum_freeze_max_age is set to its maximu
On Thu, Sep 13, 2012 at 11:36:56PM +0200, Christian Ullrich wrote:
> * Bruce Momjian wrote:
>
> >On Thu, Sep 13, 2012 at 02:15:00PM +0200, Christian Ullrich wrote:
>
> >>c:\Daten>path
> >>PATH=c:\windows;c:\windows\system32;c:\Program Files\PostgreSQL\9.2\bin
> >>
> >>c:\Daten>pg_upgrade --old-bi
I am trying to test the upgrade from my 9.1.3 db to 9.2 on ubuntu 10.10
server. I got error below when run the pg_upgrade command. What can I do
for this?
$ /opt/PostgreSQL/9.2/bin/pg_upgrade -b /opt/PostgreSQL/9.1/bin -B
/opt/PostgreSQL/9.2/bin -d /raid/pgsql -D /raid/pg92data
Performing Con
19 matches
Mail list logo
