Skip site navigation (1) Skip section navigation (2)

Installation glitches

From: Bastian Kleineidam <calvin(at)cs(dot)uni-sb(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Installation glitches
Date: 1999-11-23 12:54:34
Message-ID: Pine.LNX.4.21.9911231353380.1584-100000@void.cs.uni-sb.de (view raw or flat)
Thread:
Lists: pgsql-bugs
Your name               :       Bastian Kleineidam
Your email address      :	calvin(at)cs(dot)uni-sb(dot)de


System Configuration
---------------------
  Architecture (example: Intel Pentium)         : Intel Celeron 433 MHz

  Operating System (example: Linux 2.0.26 ELF)  : Linux 2.2.13 ELF

  PostgreSQL version (example: PostgreSQL-6.5.3): PostgreSQL-6.5.3 

  Compiler used (example:  gcc 2.8.0)           : gcc 2.95.2


Experiences installing PostgreSQL 6.5.3 under Debian Linux 'potato(unstable)'

(1) INSTALL step 18. (calling initdb)
    I have a non-privileged account with user postgres, group postgres
    (uid=31, gid=32).
    Everything went ok until i called initdb: this script tests
    for uid==0 but INSTALL explicitly allows installation from
    "non-privileged" accounts. This is a contradiction.

    Fix: remove the test for uid==0:
    #if [ $POSTGRES_SUPERUID -ne `pg_id` -a `pg_id` -ne 0 ]; then
    if [ $POSTGRES_SUPERUID -ne `pg_id` ]; then
    
    Then run initdb -u postgres and off you go.

(2) INSTALL step 20.c. (call psql)

======= begin shell snippet ===========
postgres(at)treasure:/~> psql
Connection to database 'postgres' failed.
FATAL 1:  Database postgres does not exist in pg_database

postgres(at)treasure:/~> psql template1
Welcome to the POSTGRESQL interactive sql monitor:
  Please read the file COPYRIGHT for copyright terms of POSTGRESQL
[PostgreSQL 6.5.3 on i686-pc-linux-gnu, compiled by gcc 2.95.2]

   type \? for help on slash commands
   type \q to quit
   type \g or terminate with semicolon to execute query
 You are currently connected to the database: template1

template1=> 
======= end shell snippet ==========

    Apparently the createdb command creates 'template1' database per
    default and the psql command connects to 'postgres' per default.
    Workaround is seen in the shell snippet: call 'psql template1'



Bastian Kleineidam


pgsql-bugs by date

Next:From: Rene HogendoornDate: 1999-11-23 15:31:01
Subject: ecpg sqlca.h bug
Previous:From: Tom LaneDate: 1999-11-23 07:49:13
Subject: Re: [BUGS] postmaster crashing on semi large tabl

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group