sql-ledger-users — SQL-Ledger users

Re: no change capabilty for a transaction

[<ke...@dk...>]

What I am looking for is something like what Nebosja is
describing, that the very nice correcting capabilities 
in sql-ledger be retained, buth that there is a facility 
to mark all transactions as "unchangeable" at a certain
point in time, eg when you have finished all bookkeeping
for a month, a quarter or a year.

I think this is a useful feature, and as reported here it seems
to be a legal requirement in a number of countries, for bigger firms.

Kind regards
keld

On Sat, Nov 03, 2001 at 06:57:10PM +0100, Nebojsa Joncic wrote:
> No in Switzerland you can change the transaction after it was entered, 
> but not after balance (quarterly or yearly) was done.
> 
> Nebojsa
> 03.11.2001 18:20:57, Keld J?rn Simonsen <ke...@dk...> wrote:
> 
> >Hi !
> >
> >I talked with Dieter about a need for not being
> >able to change a transaction, once it has been entered. 
> >This is a requirement by Danish law, so it is important
> >for Danes sql-ledger users to have that capability.
> >
> >I wonder if this is a requirement on other countries.
> >Does anyone out there have information on this?
> >
> >Kind regards
> >Keld Simonsen
> >
> 
> 
> 

Re: no change capabilty for a transaction

[Nebojsa J. <nj...@ci...>]

No in Switzerland you can change the transaction after it was entered, 
but not after balance (quarterly or yearly) was done.

Nebojsa
03.11.2001 18:20:57, Keld J?rn Simonsen <ke...@dk...> wrote:

>Hi !
>
>I talked with Dieter about a need for not being
>able to change a transaction, once it has been entered. 
>This is a requirement by Danish law, so it is important
>for Danes sql-ledger users to have that capability.
>
>I wonder if this is a requirement on other countries.
>Does anyone out there have information on this?
>
>Kind regards
>Keld Simonsen
>

no change capabilty for a transaction

[<ke...@dk...>]

Hi !

I talked with Dieter about a need for not being
able to change a transaction, once it has been entered. 
This is a requirement by Danish law, so it is important
for Danes sql-ledger users to have that capability.

I wonder if this is a requirement on other countries.
Does anyone out there have information on this?

Kind regards
Keld Simonsen

SQL-Ledger Installation

[Peter D. <mer...@ma...>]

Thanks
I've installed SQL-Ledger succesfully. Created Polish locale without=20=

problem,
so I could start work on Polish translation and do some tests
Peter Dabrowski

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Fri, 2 Nov 2001, Oscar Buijten wrote:

> [root@euro oscar]# rpm -i perl-DBI-1.14-4mdk.i586.rpm
> [root@euro oscar]# rpm -i perl-DBD-Pg-0.91-2mdk.i586.rpm

> Looks like I am back to square 1....
>=20
> Any suggestions???

Hi Oscar,

rpm -e all of these rpms.  Let's do it by hand, one at a time.
Grab DBI and DBD (or if you want I'll email them to you.)

Unpack each archive into /usr/local/src (as root)
cd /usr/local/src/DBI* (he goes first)
perl Makefile.PL
make
make install

repeat the process for DBD...trust me it makes sense to remove=20
mandrake/redhat's rpm (redhat package mangler) from the equation.
Let's let perl do it's job.  It will complain if something is
amiss.

--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Oscar B. <os...@el...>]

Sorry Paulo,

Sounds like a bad idea. The following is in it.
[root@euro data]# ls -l
total 192
-rw-------    1 40       41              4 Jun 11 16:47 PG_VERSION
-rw-------    1 40       41           8192 Oct 30 05:09 pg_control
-rw-------    1 40       41           8192 Oct 30 17:04 pg_database
-r--------    1 40       41           3407 Jun 11 16:47 pg_geqo.sample
-rw-------    1 40       41           8192 Oct 30 18:28 pg_group
-rw-------    1 40       41          16384 Oct 28 18:01 pg_group_name_index
-rw-------    1 40       41          16384 Oct 28 18:01 pg_group_sysid_index
-r--------    1 40       41           5794 Jun 20 10:37 pg_hba.conf
-r--------    1 root     root         5827 Jun 20 10:25 pg_hba.conf~
-rw-------    1 40       41          65536 Oct 30 20:57 pg_log
-rwx------    1 root     root           44 Jun 20 11:32 pg_options~*
-rw-------    1 40       41             35 Oct 28 18:01 pg_pwd
-rw-------    1 40       41              0 Oct 28 18:01 pg_pwd.reload
-rw-------    1 40       41           8192 Oct 28 18:01 pg_shadow
-rw-------    1 40       41           8192 Oct 30 20:57 pg_variable
drwx------    2 40       41           4096 Jun 11 16:47 pg_xlog/
-rw-------    1 40       41             87 Oct 30 05:09 postmaster.opts
-r--------    1 40       41              1 Jun 11 16:47 
postmaster.opts.default
-rw-------    1 root     root           84 Jun 20 11:15 postmaster.opts~
-rw-------    1 40       41              4 Oct 30 05:09 postmaster.pid

I used to have a directory (in v7.0.3)
/var/lib/pgsql/data/base

I don't know if i is entirely correct, but I have changed the PGDATA env 
variable to: PGDATA=/var/lib/pgsql/data
I have run initdb and it seemed to do what it had to do.
Have strted the server with the scrpts of Thomas.
[root@euro /root]# ./pgstart.sh
Starting postgres service...postmaster: pid [2579] started...

This is what is in the log file:

  cat /home/oscar/postgres.log
DEBUG:  database system was shut down at 2001-11-02 15:32:29 CET
DEBUG:  CheckPoint record at (0, 1522080)
DEBUG:  Redo record at (0, 1522080); Undo record at (0, 0); Shutdown TRUE
DEBUG:  NextTransactionId: 615; NextOid: 18720
DEBUG:  database system is in production state

I have restored the databases with:
postgres-# \i alldata.backup

That seems to have worked.

****************************************************************

So now I have tried to do the following:

[root@euro oscar]# rpm -i perl-DBI-1.14-4mdk.i586.rpm

[root@euro oscar]# rpm -i perl-DBD-Pg-0.91-2mdk.i586.rpm

[root@euro oscar]# perl testdbi.pl (your little test script Thomas)

install_driver(Pg) failed: Can't locate DBD/Pg.pm in @INC (@INC 
contains: /usr/local/lib/perl5/5.6.1/i686-linux 
/usr/local/lib/perl5/5.6.1 
/usr/local/lib/perl5/site_perl/5.6.1/i686-linux 
/usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl .) 
at (eval 1) line 3.
Perhaps the DBD::Pg perl module hasn't been fully installed,
or perhaps the capitalisation of 'Pg' isn't right.
Available drivers: ExampleP, Proxy.
  at testdbi.pl line 3

Looks like I am back to square 1....

Any suggestions???

Thanks,



Oscar



Paulo Rodrigues wrote:

> Oscar Buijten wrote:
> 
>>Hi Paulo,
>>
>>Thanks for your interest :-)
>>
>>I didn't yet.
>>This is the result:
>>
>>[root@euro conf]# su - postgres
>>[postgres@euro pgsql]$ initdb
>>This database system will be initialized with username "postgres".
>>This user will own all the data files and must also own the server process.
>>
>>initdb: The directory /var/lib/pgsql/data exists but is not empty.
>>If you want to create a new database system, either remove or empty
>>the directory /var/lib/pgsql/data or run initdb with
>>an argument other than /var/lib/pgsql/data.
>>
>>What do I do with that?
>>
>>Thanks,
>>
>>Oscar
>>
>>Paulo Rodrigues wrote:
>>
>>
>>>Oscar Buijten wrote:
>>>[HUGE SNIP]
>>>
>>>Hello Oscar,
>>>
>>>did you run initdb? Sorry I couldn't find a reference to it in your
>>>email.
>>>
>>>Paulo
>>>
>>>
>>>
>>--
>>_____________________________________________________________
>>
>>Oscar Buijten
>>
>>Tel: +33.4.67.57.97.45
>>Fax: +33.4.67.57.97.46
>>GSM: +33.6.20.84.15.22
>>
>>Email: os...@el...
>>
>>Web:   www.elbie.com
>>
> 
> Hi
> 
> you have no data in there, right? flush that dir: rm -rf
> /var/lib/pgsql/data and try again the initdb
> 
> good luck
> Paulo
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Paulo R. <pro...@vi...>]

Oscar Buijten wrote:
>=20
> Hi Paulo,
>=20
> Thanks for your interest :-)
>=20
> I didn't yet.
> This is the result:
>=20
> [root@euro conf]# su - postgres
> [postgres@euro pgsql]$ initdb
> This database system will be initialized with username "postgres".
> This user will own all the data files and must also own the server proc=
ess.
>=20
> initdb: The directory /var/lib/pgsql/data exists but is not empty.
> If you want to create a new database system, either remove or empty
> the directory /var/lib/pgsql/data or run initdb with
> an argument other than /var/lib/pgsql/data.
>=20
> What do I do with that?
>=20
> Thanks,
>=20
> Oscar
>=20
> Paulo Rodrigues wrote:
>=20
> > Oscar Buijten wrote:
> > [HUGE SNIP]
> >
> > Hello Oscar,
> >
> > did you run initdb? Sorry I couldn't find a reference to it in your
> > email.
> >
> > Paulo
> >
> >
>=20
> --
> _____________________________________________________________
>=20
> Oscar Buijten
>=20
> Tel: +33.4.67.57.97.45
> Fax: +33.4.67.57.97.46
> GSM: +33.6.20.84.15.22
>=20
> Email: os...@el...
>=20
> Web:   www.elbie.com

Hi

you have no data in there, right? flush that dir: rm -rf
/var/lib/pgsql/data and try again the initdb

good luck
Paulo

--=20
Paulo Rodrigues
Professional Services / MIS
pro...@vi...

VIA NET.WORKS Portugal
http://www.vianetworks.pt
local touch global reach
-------------------------
Sabe quem tem acesso =E0 rede da sua empresa?
http://security.vianetworks.pt/sig/

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Oscar B. <os...@el...>]

Hi Paulo,

Thanks for your interest :-)

I didn't yet.
This is the result:

[root@euro conf]# su - postgres
[postgres@euro pgsql]$ initdb
This database system will be initialized with username "postgres".
This user will own all the data files and must also own the server process.

initdb: The directory /var/lib/pgsql/data exists but is not empty.
If you want to create a new database system, either remove or empty
the directory /var/lib/pgsql/data or run initdb with
an argument other than /var/lib/pgsql/data.

What do I do with that?

Thanks,

Oscar

Paulo Rodrigues wrote:

> Oscar Buijten wrote:
> [HUGE SNIP]
> 
> Hello Oscar,
> 
> did you run initdb? Sorry I couldn't find a reference to it in your
> email.
> 
> Paulo
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Paulo R. <pro...@vi...>]

Oscar Buijten wrote:
[HUGE SNIP]

Hello Oscar,

did you run initdb? Sorry I couldn't find a reference to it in your
email.

Paulo

--=20
Paulo Rodrigues
Professional Services / MIS
pro...@vi...

VIA NET.WORKS Portugal
http://www.vianetworks.pt
local touch global reach
-------------------------
Sabe quem tem acesso =E0 rede da sua empresa?
http://security.vianetworks.pt/sig/

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Oscar B. <os...@el...>]

Hi Thomas,

No problem!

Grrrr.... Not there yet.
This mail is a bit long, but I thought it would be best to provide details.

Tried your start script.
The logfile then says:
[root@euro /root]# cat /home/oscar/postgres.log
postmaster does not find the database system.
         Expected to find it in the PGDATA directory "/var/lib/pgsql/data",
         but unable to open file 
"/var/lib/pgsql/data/global/pg_control": No such file or directory

[root@euro /root]#

locate pg-control says:

/var/lib/pgsql/data/pg_control
/usr/lib/pgsql/contrib/pg_controldata
/usr/lib/pgsql/contrib/pg_controldata/README.pg_controldata
/usr/lib/pgsql/contrib/pg_controldata/pg_controldata
/usr/lib/pgsql/contrib/pg_controldata/pg_controldata.c
/usr/lib/pgsql/contrib/pg_controldata/pg_controldata.o
/usr/lib/pgsql/contrib/pg_controldata/pg_crc.o
/usr/lib/pgsql/contrib/pg_controldata/pg_crc.c

then:

[root@euro data]# cd /var/lib/pgsql/data/
[root@euro data]# ls -l
total 192
-rw-------    1 40       41              4 Jun 11 16:47 PG_VERSION
-rw-------    1 40       41           8192 Oct 30 05:09 pg_control
-rw-------    1 40       41           8192 Oct 30 17:04 pg_database
-r--------    1 40       41           3407 Jun 11 16:47 pg_geqo.sample
-rw-------    1 40       41           8192 Oct 30 18:28 pg_group
-rw-------    1 40       41      16384 Oct 28 18:01 pg_group_name_index
-rw-------    1 40       41      16384 Oct 28 18:01 pg_group_sysid_index
-r--------    1 40       41           5794 Jun 20 10:37 pg_hba.conf
-r--------    1 root     root         5827 Jun 20 10:25 pg_hba.conf~
-rw-------    1 40       41          65536 Oct 30 20:57 pg_log
-rwx------    1 root     root           44 Jun 20 11:32 pg_options~*
-rw-------    1 40       41             35 Oct 28 18:01 pg_pwd
-rw-------    1 40       41              0 Oct 28 18:01 pg_pwd.reload
-rw-------    1 40       41           8192 Oct 28 18:01 pg_shadow
-rw-------    1 40       41           8192 Oct 30 20:57 pg_variable
drwx------    2 40       41           4096 Jun 11 16:47 pg_xlog/
-rw-------    1 40       41             87 Oct 30 05:09 postmaster.opts
-r--------    1 40       41       1 Jun 11 16:47 postmaster.opts.default
-rw-------    1 root     root           84 Jun 20 11:15 postmaster.opts~
-rw-------    1 40       41              4 Oct 30 05:09 postmaster.pid

I used to have a subdirectory 'base' in there with all the databases...
No 'global' directory to find either.

Extract of: cat /etc/profile

export PGDATA=/var/lib/pgsql/data
export POSTGRES_INCLUDE=/usr/include/pgsql
export POSTGRES_LIB=/usr/lib/pgsql
export PGLIB=/usr/lib/pgsql/contrib

Which is based on: locate pgsql

/etc/pgsql
/etc/pgsql/odbcinst.ini
/var/lib/pgsql
/var/lib/pgsql/backups
/var/lib/pgsql/data
/var/lib/pgsql/data/pg_xlog
/var/lib/pgsql/data/pg_control
/var/lib/pgsql/data/pg_variable
/var/lib/pgsql/data/pg_group
/var/lib/pgsql/data/pg_group_name_index
/var/lib/pgsql/data/pg_group_sysid_index
/var/lib/pgsql/data/pg_database
/var/lib/pgsql/data/pg_shadow
/var/lib/pgsql/data/pg_log
/var/lib/pgsql/data/PG_VERSION
/var/lib/pgsql/data/pg_hba.conf
/var/lib/pgsql/data/pg_geqo.sample
/var/lib/pgsql/data/postmaster.opts.default
/var/lib/pgsql/data/postmaster.pid
/var/lib/pgsql/data/postmaster.opts
/var/lib/pgsql/data/pg_hba.conf~
/var/lib/pgsql/data/pg_pwd
/var/lib/pgsql/data/pg_pwd.reload
/var/lib/pgsql/data/postmaster.opts~
/var/lib/pgsql/data/pg_options~
/var/lib/pgsql/.bashrc
/var/lib/pgsql/.bash_profile
/var/lib/pgsql/.bash_profile.rpmnew
/var/lib/pgsql/initdb.i18n
/var/log/pgsql
/usr/share/doc/postgresql-7.1.3/html/plpgsql-description.html
/usr/share/doc/postgresql-7.1.3/html/plpgsql-examples.html
/usr/share/doc/postgresql-7.1.3/html/plpgsql-porting.html
/usr/share/doc/postgresql-7.1.3/html/plpgsql-trigger.html
/usr/share/doc/postgresql-7.1.3/html/plpgsql.html
/usr/share/doc/php-pgsql-4.0.4pl1
/usr/share/doc/php-pgsql-4.0.4pl1/README
/usr/share/pgsql
/usr/share/pgsql/jdbc7.0-1.1.jar
/usr/share/pgsql/jdbc7.1-1.2.jar
/usr/share/pgsql/odbc.sql
/usr/share/pgsql/perl5
/usr/share/pgsql/perl5/test.pl
/usr/share/pgsql/backup
/usr/share/pgsql/backup/pg_dumpall_new
/usr/share/pgsql/global.bki
/usr/share/pgsql/global.description
/usr/share/pgsql/pg_hba.conf.sample
/usr/share/pgsql/pg_ident.conf.sample
/usr/share/pgsql/postgresql.conf.sample
/usr/share/pgsql/template1.bki
/usr/share/pgsql/template1.description
/usr/lib/pgsql
/usr/lib/pgsql/plpgsql.so
/usr/lib/pgsql/contrib
/usr/lib/pgsql/contrib/README
/usr/lib/pgsql/contrib/array
/usr/lib/pgsql/contrib/array/README.array_iterator
/usr/lib/pgsql/contrib/array/array_iterator.c
/usr/lib/pgsql/contrib/array/array_iterator.h
/usr/lib/pgsql/contrib/array/array_iterator.so
/usr/lib/pgsql/contrib/array/array_iterator.sql
/usr/lib/pgsql/contrib/array/array_iterator.sql.in
/usr/lib/pgsql/contrib/chkpass
/usr/lib/pgsql/contrib/chkpass/README.chkpass
/usr/lib/pgsql/contrib/chkpass/chkpass.c
/usr/lib/pgsql/contrib/chkpass/chkpass.sql
/usr/lib/pgsql/contrib/cube
/usr/lib/pgsql/contrib/cube/README.cube
/usr/lib/pgsql/contrib/cube/buffer.c
/usr/lib/pgsql/contrib/cube/buffer.h
/usr/lib/pgsql/contrib/cube/buffer.o
/usr/lib/pgsql/contrib/cube/cube.c
/usr/lib/pgsql/contrib/cube/cube.o
/usr/lib/pgsql/contrib/cube/cube.sql
/usr/lib/pgsql/contrib/cube/cube.sql.in
/usr/lib/pgsql/contrib/cube/cubedata.h
/usr/lib/pgsql/contrib/cube/cubeparse.c
/usr/lib/pgsql/contrib/cube/cubeparse.h
/usr/lib/pgsql/contrib/cube/cubeparse.o
/usr/lib/pgsql/contrib/cube/cubeparse.y
/usr/lib/pgsql/contrib/cube/cubescan.c
/usr/lib/pgsql/contrib/cube/cubescan.l
/usr/lib/pgsql/contrib/cube/cubescan.o
/usr/lib/pgsql/contrib/cube/data
/usr/lib/pgsql/contrib/cube/data/test_cube.data
/usr/lib/pgsql/contrib/cube/expected
/usr/lib/pgsql/contrib/cube/expected/cube.out
/usr/lib/pgsql/contrib/cube/libcube.a
/usr/lib/pgsql/contrib/cube/libcube.so
/usr/lib/pgsql/contrib/cube/libcube.so.1
/usr/lib/pgsql/contrib/cube/libcube.so.1.0
/usr/lib/pgsql/contrib/cube/sql
/usr/lib/pgsql/contrib/cube/sql/cube.sql
/usr/lib/pgsql/contrib/earthdistance
/usr/lib/pgsql/contrib/earthdistance/README.earthdistance
/usr/lib/pgsql/contrib/earthdistance/earthdistance.c
/usr/lib/pgsql/contrib/earthdistance/earthdistance.so
/usr/lib/pgsql/contrib/earthdistance/earthdistance.sql
/usr/lib/pgsql/contrib/earthdistance/earthdistance.sql.in
/usr/lib/pgsql/contrib/findoidjoins
/usr/lib/pgsql/contrib/findoidjoins/README.findoidjoins
/usr/lib/pgsql/contrib/findoidjoins/findoidjoins
/usr/lib/pgsql/contrib/findoidjoins/findoidjoins.c
/usr/lib/pgsql/contrib/findoidjoins/findoidjoins.o
/usr/lib/pgsql/contrib/findoidjoins/make_oidjoins_check
/usr/lib/pgsql/contrib/fulltextindex
/usr/lib/pgsql/contrib/fulltextindex/README.fti
/usr/lib/pgsql/contrib/fulltextindex/TODO
/usr/lib/pgsql/contrib/fulltextindex/fti.c
/usr/lib/pgsql/contrib/fulltextindex/fti.pl
/usr/lib/pgsql/contrib/fulltextindex/fti.so
/usr/lib/pgsql/contrib/fulltextindex/fti.sql
/usr/lib/pgsql/contrib/fulltextindex/fti.sql.in
/usr/lib/pgsql/contrib/fulltextindex/timings.sh
/usr/lib/pgsql/contrib/intarray
/usr/lib/pgsql/contrib/intarray/README.intarray
/usr/lib/pgsql/contrib/intarray/_int.c
/usr/lib/pgsql/contrib/intarray/_int.o
/usr/lib/pgsql/contrib/intarray/_int.sql
/usr/lib/pgsql/contrib/intarray/_int.sql.in
/usr/lib/pgsql/contrib/intarray/bench
/usr/lib/pgsql/contrib/intarray/bench/bench.pl
/usr/lib/pgsql/contrib/intarray/bench/create_test.pl
/usr/lib/pgsql/contrib/intarray/data
/usr/lib/pgsql/contrib/intarray/data/test__int.data
/usr/lib/pgsql/contrib/intarray/expected
/usr/lib/pgsql/contrib/intarray/expected/_int.out
/usr/lib/pgsql/contrib/intarray/lib_int.a
/usr/lib/pgsql/contrib/intarray/lib_int.so
/usr/lib/pgsql/contrib/intarray/lib_int.so.1
/usr/lib/pgsql/contrib/intarray/lib_int.so.1.0
/usr/lib/pgsql/contrib/intarray/sql
/usr/lib/pgsql/contrib/intarray/sql/_int.sql
/usr/lib/pgsql/contrib/ipc_check
/usr/lib/pgsql/contrib/ipc_check/README
/usr/lib/pgsql/contrib/ipc_check/ipc_check.pl
/usr/lib/pgsql/contrib/isbn_issn
/usr/lib/pgsql/contrib/isbn_issn/README.isbn_issn
/usr/lib/pgsql/contrib/isbn_issn/isbn_issn.c
/usr/lib/pgsql/contrib/isbn_issn/isbn_issn.so
/usr/lib/pgsql/contrib/isbn_issn/isbn_issn.sql
/usr/lib/pgsql/contrib/isbn_issn/isbn_issn.sql.in
/usr/lib/pgsql/contrib/lo
/usr/lib/pgsql/contrib/lo/README.lo
/usr/lib/pgsql/contrib/lo/lo.c
/usr/lib/pgsql/contrib/lo/lo.so
/usr/lib/pgsql/contrib/lo/lo.sql
/usr/lib/pgsql/contrib/lo/lo.sql.in
/usr/lib/pgsql/contrib/lo/lo_drop.sql
/usr/lib/pgsql/contrib/lo/lo_test.sql
/usr/lib/pgsql/contrib/mSQL-interface
/usr/lib/pgsql/contrib/mSQL-interface/README.mpgsql
/usr/lib/pgsql/contrib/mSQL-interface/mpgsql.c
/usr/lib/pgsql/contrib/mac
/usr/lib/pgsql/contrib/mac/README.mac
/usr/lib/pgsql/contrib/mac/createoui
/usr/lib/pgsql/contrib/mac/dropoui
/usr/lib/pgsql/contrib/mac/ouiparse.awk
/usr/lib/pgsql/contrib/mac/updateoui
/usr/lib/pgsql/contrib/miscutil
/usr/lib/pgsql/contrib/miscutil/README.misc_utils
/usr/lib/pgsql/contrib/miscutil/misc_utils.c
/usr/lib/pgsql/contrib/miscutil/misc_utils.h
/usr/lib/pgsql/contrib/miscutil/misc_utils.so
/usr/lib/pgsql/contrib/miscutil/misc_utils.sql
/usr/lib/pgsql/contrib/miscutil/misc_utils.sql.in
/usr/lib/pgsql/contrib/mysql
/usr/lib/pgsql/contrib/mysql/README
/usr/lib/pgsql/contrib/mysql/my2pg.pl
/usr/lib/pgsql/contrib/mysql/mysql2pgsql
/usr/lib/pgsql/contrib/noupdate
/usr/lib/pgsql/contrib/noupdate/README.noup
/usr/lib/pgsql/contrib/noupdate/noup.c
/usr/lib/pgsql/contrib/noupdate/noup.so
/usr/lib/pgsql/contrib/noupdate/noup.sql
/usr/lib/pgsql/contrib/noupdate/noup.sql.in
/usr/lib/pgsql/contrib/oid2name
/usr/lib/pgsql/contrib/oid2name/README.oid2name
/usr/lib/pgsql/contrib/oid2name/oid2name
/usr/lib/pgsql/contrib/oid2name/oid2name.c
/usr/lib/pgsql/contrib/oid2name/oid2name.o
/usr/lib/pgsql/contrib/pg_controldata
/usr/lib/pgsql/contrib/pg_controldata/README.pg_controldata
/usr/lib/pgsql/contrib/pg_controldata/pg_controldata
/usr/lib/pgsql/contrib/pg_controldata/pg_controldata.c
/usr/lib/pgsql/contrib/pg_controldata/pg_controldata.o
/usr/lib/pgsql/contrib/pg_controldata/pg_crc.o
/usr/lib/pgsql/contrib/pg_controldata/pg_crc.c
/usr/lib/pgsql/contrib/pg_dumplo
/usr/lib/pgsql/contrib/pg_dumplo/README.pg_dumplo
/usr/lib/pgsql/contrib/pg_dumplo/lo_export.c
/usr/lib/pgsql/contrib/pg_dumplo/lo_export.o
/usr/lib/pgsql/contrib/pg_dumplo/lo_import.c
/usr/lib/pgsql/contrib/pg_dumplo/lo_import.o
/usr/lib/pgsql/contrib/pg_dumplo/main.c
/usr/lib/pgsql/contrib/pg_dumplo/main.o
/usr/lib/pgsql/contrib/pg_dumplo/pg_dumplo
/usr/lib/pgsql/contrib/pg_dumplo/pg_dumplo.h
/usr/lib/pgsql/contrib/pg_dumplo/utils.c
/usr/lib/pgsql/contrib/pg_dumplo/utils.o
/usr/lib/pgsql/contrib/pg_logger
/usr/lib/pgsql/contrib/pg_logger/README.pg_logger
/usr/lib/pgsql/contrib/pg_logger/pg_logger
/usr/lib/pgsql/contrib/pg_logger/pg_logger.c
/usr/lib/pgsql/contrib/pg_logger/pg_logger.o
/usr/lib/pgsql/contrib/pg_resetxlog
/usr/lib/pgsql/contrib/pg_resetxlog/README.pg_resetxlog
/usr/lib/pgsql/contrib/pg_resetxlog/pg_crc.c
/usr/lib/pgsql/contrib/pg_resetxlog/pg_crc.o
/usr/lib/pgsql/contrib/pg_resetxlog/pg_resetxlog
/usr/lib/pgsql/contrib/pg_resetxlog/pg_resetxlog.c
/usr/lib/pgsql/contrib/pg_resetxlog/pg_resetxlog.o
/usr/lib/pgsql/contrib/pgbench
/usr/lib/pgsql/contrib/pgbench/README.pgbench
/usr/lib/pgsql/contrib/pgbench/README.pgbench_jis
/usr/lib/pgsql/contrib/pgbench/pgbench
/usr/lib/pgsql/contrib/pgbench/pgbench.c
/usr/lib/pgsql/contrib/pgbench/pgbench.o
/usr/lib/pgsql/contrib/pgcrypto
/usr/lib/pgsql/contrib/pgcrypto/README.pgcrypto
/usr/lib/pgsql/contrib/pgcrypto/encode.c
/usr/lib/pgsql/contrib/pgcrypto/encode.h
/usr/lib/pgsql/contrib/pgcrypto/encode.o
/usr/lib/pgsql/contrib/pgcrypto/internal.c
/usr/lib/pgsql/contrib/pgcrypto/internal.o
/usr/lib/pgsql/contrib/pgcrypto/krb.c
/usr/lib/pgsql/contrib/pgcrypto/libpgcrypto.a
/usr/lib/pgsql/contrib/pgcrypto/libpgcrypto.so
/usr/lib/pgsql/contrib/pgcrypto/libpgcrypto.so.0
/usr/lib/pgsql/contrib/pgcrypto/libpgcrypto.so.0.1
/usr/lib/pgsql/contrib/pgcrypto/md5.c
/usr/lib/pgsql/contrib/pgcrypto/md5.h
/usr/lib/pgsql/contrib/pgcrypto/md5.o
/usr/lib/pgsql/contrib/pgcrypto/mhash.c
/usr/lib/pgsql/contrib/pgcrypto/openssl.c
/usr/lib/pgsql/contrib/pgcrypto/pgcrypto.c
/usr/lib/pgsql/contrib/pgcrypto/pgcrypto.h
/usr/lib/pgsql/contrib/pgcrypto/pgcrypto.o
/usr/lib/pgsql/contrib/pgcrypto/pgcrypto.sql
/usr/lib/pgsql/contrib/pgcrypto/pgcrypto.sql.in
/usr/lib/pgsql/contrib/pgcrypto/sha1.c
/usr/lib/pgsql/contrib/pgcrypto/sha1.h
/usr/lib/pgsql/contrib/pgcrypto/sha1.o
/usr/lib/pgsql/contrib/retep
/usr/lib/pgsql/contrib/retep/CHANGELOG
/usr/lib/pgsql/contrib/retep/Implementation
/usr/lib/pgsql/contrib/retep/README
/usr/lib/pgsql/contrib/retep/build.xml
/usr/lib/pgsql/contrib/retep/data
/usr/lib/pgsql/contrib/retep/data/cds.dtd
/usr/lib/pgsql/contrib/retep/data/cds.xml
/usr/lib/pgsql/contrib/retep/retep.jpx
/usr/lib/pgsql/contrib/retep/uk
/usr/lib/pgsql/contrib/retep/uk/org
/usr/lib/pgsql/contrib/retep/uk/org/retep
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DCollection.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DConstants.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DElement.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DEnvironment.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DModule.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DModuleXML.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DNode.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DProcessor.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/dtu/DTransform.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/tools
/usr/lib/pgsql/contrib/retep/uk/org/retep/tools/Tool.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/tools.properties
/usr/lib/pgsql/contrib/retep/uk/org/retep/util
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/ExceptionDialog.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/Globals.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/Logger.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/Main.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/StandaloneApp.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/hba
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/hba/Editor.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/hba/Main.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/hba/Record.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/misc
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/misc/IPAddress.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/misc/PropertiesIO.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/misc/WStringTokenizer.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/models
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/models/HBATableModel.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/models/PropertiesTableModel.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/proped
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/proped/Main.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/util/proped/PropertyEditor.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/core
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/core/XMLFactory.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/core/XMLFactoryException.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/jdbc
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/jdbc/XMLDatabase.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/jdbc/XMLResultSet.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/parser
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/parser/TagHandler.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/parser/TagListener.java
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/test
/usr/lib/pgsql/contrib/retep/uk/org/retep/xml/test/XMLExport.java
/usr/lib/pgsql/contrib/rserv
/usr/lib/pgsql/contrib/rserv/ApplySnapshot
/usr/lib/pgsql/contrib/rserv/ApplySnapshot.in
/usr/lib/pgsql/contrib/rserv/CleanLog
/usr/lib/pgsql/contrib/rserv/CleanLog.in
/usr/lib/pgsql/contrib/rserv/GetSyncID
/usr/lib/pgsql/contrib/rserv/GetSyncID.in
/usr/lib/pgsql/contrib/rserv/InitRservTest
/usr/lib/pgsql/contrib/rserv/InitRservTest.in
/usr/lib/pgsql/contrib/rserv/MasterAddTable
/usr/lib/pgsql/contrib/rserv/MasterAddTable.in
/usr/lib/pgsql/contrib/rserv/MasterInit
/usr/lib/pgsql/contrib/rserv/MasterInit.in
/usr/lib/pgsql/contrib/rserv/MasterSync
/usr/lib/pgsql/contrib/rserv/MasterSync.in
/usr/lib/pgsql/contrib/rserv/PrepareSnapshot
/usr/lib/pgsql/contrib/rserv/PrepareSnapshot.in
/usr/lib/pgsql/contrib/rserv/README.rserv
/usr/lib/pgsql/contrib/rserv/RServ.pm
/usr/lib/pgsql/contrib/rserv/Replicate
/usr/lib/pgsql/contrib/rserv/Replicate.in
/usr/lib/pgsql/contrib/rserv/RservTest
/usr/lib/pgsql/contrib/rserv/RservTest.in
/usr/lib/pgsql/contrib/rserv/SlaveAddTable
/usr/lib/pgsql/contrib/rserv/SlaveAddTable.in
/usr/lib/pgsql/contrib/rserv/SlaveInit
/usr/lib/pgsql/contrib/rserv/SlaveInit.in
/usr/lib/pgsql/contrib/rserv/master.sql
/usr/lib/pgsql/contrib/rserv/master.sql.in
/usr/lib/pgsql/contrib/rserv/regress.sh
/usr/lib/pgsql/contrib/rserv/rserv.c
/usr/lib/pgsql/contrib/rserv/rserv.so
/usr/lib/pgsql/contrib/rserv/slave.sql
/usr/lib/pgsql/contrib/rserv/slave.sql.in
/usr/lib/pgsql/contrib/seg
/usr/lib/pgsql/contrib/seg/README.seg
/usr/lib/pgsql/contrib/seg/buffer.c
/usr/lib/pgsql/contrib/seg/buffer.h
/usr/lib/pgsql/contrib/seg/buffer.o
/usr/lib/pgsql/contrib/seg/data
/usr/lib/pgsql/contrib/seg/data/test_seg.data
/usr/lib/pgsql/contrib/seg/expected
/usr/lib/pgsql/contrib/seg/expected/seg.out
/usr/lib/pgsql/contrib/seg/libseg.a
/usr/lib/pgsql/contrib/seg/libseg.so
/usr/lib/pgsql/contrib/seg/libseg.so.1
/usr/lib/pgsql/contrib/seg/libseg.so.1.0
/usr/lib/pgsql/contrib/seg/seg-validate.pl
/usr/lib/pgsql/contrib/seg/seg.c
/usr/lib/pgsql/contrib/seg/seg.o
/usr/lib/pgsql/contrib/seg/seg.sql
/usr/lib/pgsql/contrib/seg/seg.sql.in
/usr/lib/pgsql/contrib/seg/segdata.h
/usr/lib/pgsql/contrib/seg/segparse.c
/usr/lib/pgsql/contrib/seg/segparse.h
/usr/lib/pgsql/contrib/seg/segparse.o
/usr/lib/pgsql/contrib/seg/segparse.y
/usr/lib/pgsql/contrib/seg/segscan.c
/usr/lib/pgsql/contrib/seg/segscan.l
/usr/lib/pgsql/contrib/seg/segscan.o
/usr/lib/pgsql/contrib/seg/sort-segments.pl
/usr/lib/pgsql/contrib/seg/sql
/usr/lib/pgsql/contrib/seg/sql/seg.sql
/usr/lib/pgsql/contrib/soundex
/usr/lib/pgsql/contrib/soundex/README.soundex
/usr/lib/pgsql/contrib/soundex/soundex.c
/usr/lib/pgsql/contrib/soundex/soundex.so
/usr/lib/pgsql/contrib/soundex/soundex.sql
/usr/lib/pgsql/contrib/soundex/soundex.sql.in
/usr/lib/pgsql/contrib/spi
/usr/lib/pgsql/contrib/spi/README.spi
/usr/lib/pgsql/contrib/spi/autoinc.c
/usr/lib/pgsql/contrib/spi/autoinc.example
/usr/lib/pgsql/contrib/spi/autoinc.so
/usr/lib/pgsql/contrib/spi/autoinc.sql
/usr/lib/pgsql/contrib/spi/autoinc.sql.in
/usr/lib/pgsql/contrib/spi/insert_username.c
/usr/lib/pgsql/contrib/spi/insert_username.example
/usr/lib/pgsql/contrib/spi/insert_username.so
/usr/lib/pgsql/contrib/spi/insert_username.sql
/usr/lib/pgsql/contrib/spi/insert_username.sql.in
/usr/lib/pgsql/contrib/spi/moddatetime.c
/usr/lib/pgsql/contrib/spi/moddatetime.example
/usr/lib/pgsql/contrib/spi/moddatetime.so
/usr/lib/pgsql/contrib/spi/moddatetime.sql
/usr/lib/pgsql/contrib/spi/moddatetime.sql.in
/usr/lib/pgsql/contrib/spi/preprocessor
/usr/lib/pgsql/contrib/spi/preprocessor/README.MAX
/usr/lib/pgsql/contrib/spi/preprocessor/example.sql
/usr/lib/pgsql/contrib/spi/preprocessor/step1.c
/usr/lib/pgsql/contrib/spi/preprocessor/step1.e
/usr/lib/pgsql/contrib/spi/preprocessor/step2.pl
/usr/lib/pgsql/contrib/spi/refint.c
/usr/lib/pgsql/contrib/spi/refint.example
/usr/lib/pgsql/contrib/spi/refint.so
/usr/lib/pgsql/contrib/spi/refint.sql
/usr/lib/pgsql/contrib/spi/refint.sql.in
/usr/lib/pgsql/contrib/spi/timetravel.c
/usr/lib/pgsql/contrib/spi/timetravel.example
/usr/lib/pgsql/contrib/spi/timetravel.so
/usr/lib/pgsql/contrib/spi/timetravel.sql
/usr/lib/pgsql/contrib/spi/timetravel.sql.in
/usr/lib/pgsql/contrib/start-scripts
/usr/lib/pgsql/contrib/start-scripts/freebsd
/usr/lib/pgsql/contrib/start-scripts/linux
/usr/lib/pgsql/contrib/string
/usr/lib/pgsql/contrib/string/README.string_io
/usr/lib/pgsql/contrib/string/string_io.c
/usr/lib/pgsql/contrib/string/string_io.h
/usr/lib/pgsql/contrib/string/string_io.so
/usr/lib/pgsql/contrib/string/string_io.sql
/usr/lib/pgsql/contrib/string/string_io.sql.in
/usr/lib/pgsql/contrib/tips
/usr/lib/pgsql/contrib/tips/README.apachelog
/usr/lib/pgsql/contrib/tools
/usr/lib/pgsql/contrib/tools/add-emacs-variables
/usr/lib/pgsql/contrib/tools/find-sources
/usr/lib/pgsql/contrib/tools/make-tags
/usr/lib/pgsql/contrib/unixdate
/usr/lib/pgsql/contrib/unixdate/unixdate.sql
/usr/lib/pgsql/contrib/userlock
/usr/lib/pgsql/contrib/userlock/README.user_locks
/usr/lib/pgsql/contrib/userlock/user_locks.c
/usr/lib/pgsql/contrib/userlock/user_locks.h
/usr/lib/pgsql/contrib/userlock/user_locks.so
/usr/lib/pgsql/contrib/userlock/user_locks.sql
/usr/lib/pgsql/contrib/userlock/user_locks.sql.in
/usr/lib/pgsql/contrib/vacuumlo
/usr/lib/pgsql/contrib/vacuumlo/README.vacuumlo
/usr/lib/pgsql/contrib/vacuumlo/vacuumlo
/usr/lib/pgsql/contrib/vacuumlo/vacuumlo.c
/usr/lib/pgsql/contrib/vacuumlo/vacuumlo.o
/usr/lib/php/extensions/pgsql.so
/usr/include/pgsql
/usr/include/pgsql/fe-auth.c
/usr/include/pgsql/fe-auth.h
/usr/include/pgsql/fe-connect.c
/usr/include/pgsql/fe-exec.c
/usr/include/pgsql/fe-lobj.c
/usr/include/pgsql/fe-misc.c
/usr/include/pgsql/fe-print.c
/usr/include/pgsql/libpqdll.c
/usr/include/pgsql/libpqdll.def
/usr/include/pgsql/libpq-fe.h
/usr/include/pgsql/libpq-int.h
/usr/include/pgsql/libpq.rc
/usr/include/pgsql/Makefile
/usr/include/pgsql/pqexpbuffer.c
/usr/include/pgsql/pqexpbuffer.h
/usr/include/pgsql/pqsignal.c
/usr/include/pgsql/pqsignal.h
/usr/include/pgsql/README
/usr/include/pgsql/win32.h
/usr/include/pgsql/win32.mak
/usr/include/pgsql/Changes
/usr/include/pgsql/GNUmakefile
/usr/include/pgsql/Makefile.PL
/usr/include/pgsql/MANIFEST
/usr/include/pgsql/Pg.pm
/usr/include/pgsql/Pg.xs
/usr/include/pgsql/ppport.h
/usr/include/pgsql/test.pl
/usr/include/pgsql/typemap

So I guess I would need to explain postmaster to find his 'pg_control' 
in /var/lib/pgsql/data/ , but I have no idea how to do that. Or is the 
problem already in:
postmaster does not find the database system.
         Expected to find it in the PGDATA directory "/var/lib/pgsql/data"?

MANY Thanks in advance!!

Regards,

Oscar


Thomas Good wrote:

> On Tue, 30 Oct 2001, Oscar Buijten wrote:
> 
> 
>>Hi Thomas,
>>
> 
> Hi Oscar - doing our monthly billing here so I apologise for not
> getting back to you.
> 
> 
>>[root@euro init.d]# psql -V
>>psql (PostgreSQL) 7.1.3
>>
> 
> Good.
> 
> 
>>[root@euro init.d]# ./postgresql start
>>Initializing database: [  OK  ]
>>Starting postgresql service: [FAILED]
>>
>>Any good suggestions??
>>
> 
> Ok, first off, the usual approach with the rpms is to disable logging.
> That stinks as we have nothing to go by!  Usually you get an error 
> message sent to a log and that gives us somewhere to start.
> 
> Use this script to start up your database...but edit it to place
> the logfile in a directory that exists on your system (doesn't matter
> where as long as you know where it is.)
> 
> #!/bin/sh
> # 
> # SQL Clinic --- Version 1.0.0
> # Copyright(c) 2001 by Thomas Good <www.sqlclinic.net>
> #
> echo -n "Starting postgres service..."
> # edit this next line:
> echo "nohup postmaster -i > /home/postgres/postgres.log 2>&1 &" | su - postgres 
> sleep 1
> pid=`pidof postmaster`
> echo -e "postmaster: pid [$pid] started..."
> 
> Here is another script to shut down the db manually:
> 
> #!/bin/sh
> # 
> # SQL Clinic --- Version 1.0.0
> # Copyright(c) 2001 by Thomas Good <www.sqlclinic.net>
> # 
> echo -n "Stopping postgres service..."
> pid=`pidof postmaster`
> if [ "$pid" != "" ] ; then
> 	echo -n "postmaster: pid [$pid] killed."
> 	kill -TERM $pid
> 	sleep 1
> fi
> echo
> 
> 
> I also suggest you have a look at www.sqlclinic.net
> and click on Documentation.  Check out chapter 2.
> This is all about how I setup postgres.  Some of it doesn't
> apply but things will be less mysterious after you read
> through it.
> 
> Anyway, try the script (run it as root) and then have a look at
> the log file.  Maybe it will shed some light!
> --------------------------------------------------------------------
>               Saint Vincent Catholic Medical Centers                
> --------------------------------------------------------------------
> Thomas Good                          tomg@ { admin | q8 } .nrnet.org
> Programmer/Analyst                              Phone:  718-818-5528 
> Behavioral Health Services                      Fax:    718-818-5056  
> Residential Services                            Mobile: 917-282-7359  
> --------------------------------------------------------------------
> /*         Rekordmeister ist nur der FC Bayern München!           */
> --------------------------------------------------------------------
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> Hi Thomas,

Hi Oscar - doing our monthly billing here so I apologise for not
getting back to you.

> [root@euro init.d]# psql -V
> psql (PostgreSQL) 7.1.3

Good.

> [root@euro init.d]# ./postgresql start
> Initializing database: [  OK  ]
> Starting postgresql service: [FAILED]
>=20
> Any good suggestions??

Ok, first off, the usual approach with the rpms is to disable logging.
That stinks as we have nothing to go by!  Usually you get an error=20
message sent to a log and that gives us somewhere to start.

Use this script to start up your database...but edit it to place
the logfile in a directory that exists on your system (doesn't matter
where as long as you know where it is.)

#!/bin/sh
#=20
# SQL Clinic --- Version 1.0.0
# Copyright(c) 2001 by Thomas Good <www.sqlclinic.net>
#
echo -n "Starting postgres service..."
# edit this next line:
echo "nohup postmaster -i > /home/postgres/postgres.log 2>&1 &" | su - post=
gres=20
sleep 1
pid=3D`pidof postmaster`
echo -e "postmaster: pid [$pid] started..."

Here is another script to shut down the db manually:

#!/bin/sh
#=20
# SQL Clinic --- Version 1.0.0
# Copyright(c) 2001 by Thomas Good <www.sqlclinic.net>
#=20
echo -n "Stopping postgres service..."
pid=3D`pidof postmaster`
if [ "$pid" !=3D "" ] ; then
=09echo -n "postmaster: pid [$pid] killed."
=09kill -TERM $pid
=09sleep 1
fi
echo


I also suggest you have a look at www.sqlclinic.net
and click on Documentation.  Check out chapter 2.
This is all about how I setup postgres.  Some of it doesn't
apply but things will be less mysterious after you read
through it.

Anyway, try the script (run it as root) and then have a look at
the log file.  Maybe it will shed some light!
--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, John Stoddart wrote:

> Hi guys,
>=20
> Really useful discussion this. I should know, I trudged the same=20
> upgrade path not too long ago ...
>=20
> >The only hassle is recreating users but if you use a web interface
> >like sql ledger even this is no problem as the number of users is
> >generally limited (I have only nobody on pg and one or two on oracle.)
>=20
> Come to think of it, shouldn't this information be in a table so you=20
> could pg_dump it as well?

In the old days the createuser script used to have real queries in it=20
so you could see how the system catalogue was modified when a user=20
was added.  Now this script (/usr/local/pgsql/bin/createuser in my
case) is just a fancy front end to:=20
psql -c "CREATE USER $vars" template1
where $vars is the user's responses to a couple of questions.

To get the contents of pg_shadow (on which the pg_users view is based):
pg_dump -t pg_shadow template1 > dumpfile=20
will fail.  Apparently some sort of security mechanism.

But you can do this:
psql -c "create table db_shadow as select * from pg_shadow;" db-name
pg_dump -t db_shadow db-name > dumpfile  =20

--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Herb R. <he...@bu...>]

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> Mmmmm......
>
> perl testdbi.pl (yourscript) says:
>
> install_driver(Pg) failed: Can't locate DBD/Pg.pm in @INC (@INC
> contains: /usr/local/lib/perl5/5.6.1/i686-linux
> /usr/local/lib/perl5/5.6.1
> /usr/local/lib/perl5/site_perl/5.6.1/i686-linux
> /usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl .)
> at (eval 1) line 3.
> Perhaps the DBD::Pg perl module hasn't been fully installed,
> or perhaps the capitalisation of 'Pg' isn't right.
> Available drivers: ExampleP, Proxy.
>   at testdbi.pl line 3
>
>
> But:
>
> locate Pg.pm says:
>
> /home/oscar/tmp/Pg.pm
> /root/.cpan/build/DBD-Pg-1.01/Pg.pm
> /root/.cpan/build/DBD-Pg-1.01/blib/lib/DBD/Pg.pm
> /root/.cpan/build/pgsql_perl5-1.9.0/Pg.pm
> /root/.cpan/build/pgsql_perl5-1.9.0/blib/lib/Pg.pm
> /usr/lib/perl5/site_perl/5.6.0/i386-linux/DBD/Pg.pm
> /usr/lib/perl5/site_perl/5.6.0/i386-linux/Pg.pm
> /usr/lib/perl5/site_perl/5.6.0/i386-linux/DBD-Pg-0.95/Pg.pm
> /usr/lib/perl5/site_perl/5.6.0/i386-linux/DBD-Pg-0.95/blib/lib/DBD/Pg.pm
> /usr/include/pgsql/Pg.pm


Here is a down and dirty hack that might help:

ln -s /usr/lib/perl5/site_perl/5.6.0/i386-linux/ /usr/local/lib/perl5/site_perl/5.6.1/i686-linux/


-- 
Herb Richter,
Toronto, Ontario
http://www.partsandservice.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Oscar B. <os...@el...>]

Hi Thomas,

It too me some time, but this is where I am at:

[root@euro init.d]# ./postgresql status
postmaster is stopped

[root@euro init.d]# psql -V
psql (PostgreSQL) 7.1.3
contains readline, history, multibyte support
Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group
Portions Copyright (c) 1996 Regents of the University of California
Read the file COPYRIGHT or use the command \copyright to see the
usage and distribution terms.

[root@euro init.d]# ./postgresql start
Initializing database: [  OK  ]
Starting postgresql service: [FAILED]

The 1st time I installed Pg I already had problems getting it started.
Things didn't change yet....

Any good suggestions??

Thanks,


Oscar

Thomas Good wrote:

> On Tue, 30 Oct 2001, Oscar Buijten wrote:
> 
> 
>>Pg.h:17:22: libpq-fe.h: No such file or directory
>>make: *** [Pg.o] Error 1
>>
> 
>>I've seen that passing by before (yesterday). What is all that about?
>>
> 
> Oscar,
> 
> You need your Pg libraries installed to build DBD dude.
> Here is where we're at, in terms of fixing an aging version or
> upgrading:
> 
> Either reinstall the rpm (development) for postgresql that has
> the libraries that match your version string (7.0.x)
> 
> or --- dump your data and scrap 7.0, installing 7.1 and the
> postgresql-development package so you have your libraries.
> 
> Once we have the libraries (no matter which version you go with)
> DBD-Pg will compile.  These are really essential libraries so it
> is pretty dim of redhat to separate them out from the server
> package.   Anyway, you gotta have em.
> 
> I gotta have some coffee so I'll check back in a few to see how
> you made out.  
> 
> Tom
> 
> --------------------------------------------------------------------
>               Saint Vincent Catholic Medical Centers                
> --------------------------------------------------------------------
> Thomas Good                          tomg@ { admin | q8 } .nrnet.org
> Programmer/Analyst                              Phone:  718-818-5528 
> Behavioral Health Services                      Fax:    718-818-5056  
> Residential Services                            Mobile: 917-282-7359  
> --------------------------------------------------------------------
> /*         Rekordmeister ist nur der FC Bayern München!           */
> --------------------------------------------------------------------
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> Sounds like a viscious circle.
> I will trash Pg and reinstall from scratch (I have saved my databases=20
> and downloaded the rpm's already). By the way, I am using Mandrake 8.0.

This is the better way to go.  It really shouldn't take long.
Of course that's easy for me to say as I don't have to do it.  ;-)
--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Oscar B. <os...@el...>]

Sounds like a viscious circle.
I will trash Pg and reinstall from scratch (I have saved my databases 
and downloaded the rpm's already). By the way, I am using Mandrake 8.0.




Thomas Good wrote:

> On Tue, 30 Oct 2001, Oscar Buijten wrote:
> 
> 
>>Pg.h:17:22: libpq-fe.h: No such file or directory
>>make: *** [Pg.o] Error 1
>>
> 
>>I've seen that passing by before (yesterday). What is all that about?
>>
> 
> Oscar,
> 
> You need your Pg libraries installed to build DBD dude.
> Here is where we're at, in terms of fixing an aging version or
> upgrading:
> 
> Either reinstall the rpm (development) for postgresql that has
> the libraries that match your version string (7.0.x)
> 
> or --- dump your data and scrap 7.0, installing 7.1 and the
> postgresql-development package so you have your libraries.
> 
> Once we have the libraries (no matter which version you go with)
> DBD-Pg will compile.  These are really essential libraries so it
> is pretty dim of redhat to separate them out from the server
> package.   Anyway, you gotta have em.
> 
> I gotta have some coffee so I'll check back in a few to see how
> you made out.  
> 
> Tom
> 
> --------------------------------------------------------------------
>               Saint Vincent Catholic Medical Centers                
> --------------------------------------------------------------------
> Thomas Good                          tomg@ { admin | q8 } .nrnet.org
> Programmer/Analyst                              Phone:  718-818-5528 
> Behavioral Health Services                      Fax:    718-818-5056  
> Residential Services                            Mobile: 917-282-7359  
> --------------------------------------------------------------------
> /*         Rekordmeister ist nur der FC Bayern München!           */
> --------------------------------------------------------------------
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> Pg.h:17:22: libpq-fe.h: No such file or directory
> make: *** [Pg.o] Error 1

> I've seen that passing by before (yesterday). What is all that about?

Oscar,

You need your Pg libraries installed to build DBD dude.
Here is where we're at, in terms of fixing an aging version or
upgrading:

Either reinstall the rpm (development) for postgresql that has
the libraries that match your version string (7.0.x)

or --- dump your data and scrap 7.0, installing 7.1 and the
postgresql-development package so you have your libraries.

Once we have the libraries (no matter which version you go with)
DBD-Pg will compile.  These are really essential libraries so it
is pretty dim of redhat to separate them out from the server
package.   Anyway, you gotta have em.

I gotta have some coffee so I'll check back in a few to see how
you made out. =20

Tom

--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers availableB

[Oscar B. <os...@el...>]

Life ain't easy...

tar -zxvf DBD-Pg-1.01.tar.gz

[root@euro DBD-Pg-1.01]# perl Makefile.PL

Configuring Pg
Remember to actually read the README file !
OS: linux
Using DBI 1.20 installed in 
/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/auto/DBI
Checking if your kit is complete...
Looks good
Writing Makefile for DBD::Pg

[root@euro DBD-Pg-1.01]# make

cp Pg.pm blib/lib/DBD/Pg.pm
cp dbd-pg.pod blib/lib/DBD/dbd-pg.pod
/usr/bin/perl -I/usr/local/lib/perl5/5.6.1/i686-linux 
-I/usr/local/lib/perl5/5.6.1 /usr/local/lib/perl5/5.6.1/ExtUtils/xsubpp 
  -typemap /usr/local/lib/perl5/5.6.1/ExtUtils/typemap Pg.xs > Pg.xsc && 
mv Pg.xsc Pg.c
cc -c -I/usr/include 
-I/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/auto/DBI 
-fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -O2   -DVERSION=\"1.01\" -DXS_VERSION=\"1.01\" 
-fpic -I/usr/local/lib/perl5/5.6.1/i686-linux/CORE  Pg.c
In file included from Pg.xs:13:
Pg.h:17:22: libpq-fe.h: No such file or directory
make: *** [Pg.o] Error 1

I've seen that passing by before (yesterday). What is all that about?

Thanks,

Oscar


[root@euro DBD-Pg-1.01]#

Thomas Good wrote:

> On Tue, 30 Oct 2001, Oscar Buijten wrote:
> 
> 
>>So the DBD directory does not exist in perl 5.6.1
>>I guess I had to 'un-rpm' or something the older version of perl before 
>>installing the newer.
>>How can I fix this? I just copy the missing directory?
>>Oops! I've just tried that! That didn't help.
>>
>>Any suggestions?
>>
> 
> Grab DBD-Pg from CPAN and unpack it into /usr/local/src.
> 
> # cd /usr/local/src/DBD*
> # perl Makefile.PL
> # make 
> # make install
> 
> Then run my script again.  It should work at this point.
> When you've finished and got a working system we can talk about
> breaking it (briefly ;-) by doing an upgrade to 7.1.3
> 
> Here is something else 7.0 can't do:
> 
> SELECT fname, lname, move_in 
> FROM tracker RIGHT JOIN client_placement 
> USING (client_id)
> WHERE move_out IS NULL 
> AND dept_id = 1008
> AND track_id = 1;
> 
> That's an OUTER JOIN.  Very handy.  Now if we can only get DROP COLMUN
> I'll be satisified!  ;-)
> 
> Good luck with DBD.  Fire away if you get stuck.
> --------------------------------------------------------------------
>               Saint Vincent Catholic Medical Centers                
> --------------------------------------------------------------------
> Thomas Good                          tomg@ { admin | q8 } .nrnet.org
> Programmer/Analyst                              Phone:  718-818-5528 
> Behavioral Health Services                      Fax:    718-818-5056  
> Residential Services                            Mobile: 917-282-7359  
> --------------------------------------------------------------------
> /*         Rekordmeister ist nur der FC Bayern München!           */
> --------------------------------------------------------------------
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers availableB

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> So the DBD directory does not exist in perl 5.6.1
> I guess I had to 'un-rpm' or something the older version of perl before=
=20
> installing the newer.
> How can I fix this? I just copy the missing directory?
> Oops! I've just tried that! That didn't help.
>=20
> Any suggestions?

Grab DBD-Pg from CPAN and unpack it into /usr/local/src.

# cd /usr/local/src/DBD*
# perl Makefile.PL
# make=20
# make install

Then run my script again.  It should work at this point.
When you've finished and got a working system we can talk about
breaking it (briefly ;-) by doing an upgrade to 7.1.3

Here is something else 7.0 can't do:

SELECT fname, lname, move_in=20
FROM tracker RIGHT JOIN client_placement=20
USING (client_id)
WHERE move_out IS NULL=20
AND dept_id =3D 1008
AND track_id =3D 1;

That's an OUTER JOIN.  Very handy.  Now if we can only get DROP COLMUN
I'll be satisified!  ;-)

Good luck with DBD.  Fire away if you get stuck.
--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Oscar B. <os...@el...>]

Mmmmm......

perl testdbi.pl (yourscript) says:

install_driver(Pg) failed: Can't locate DBD/Pg.pm in @INC (@INC 
contains: /usr/local/lib/perl5/5.6.1/i686-linux 
/usr/local/lib/perl5/5.6.1 
/usr/local/lib/perl5/site_perl/5.6.1/i686-linux 
/usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl .) 
at (eval 1) line 3.
Perhaps the DBD::Pg perl module hasn't been fully installed,
or perhaps the capitalisation of 'Pg' isn't right.
Available drivers: ExampleP, Proxy.
  at testdbi.pl line 3


But:

locate Pg.pm says:

/home/oscar/tmp/Pg.pm
/root/.cpan/build/DBD-Pg-1.01/Pg.pm
/root/.cpan/build/DBD-Pg-1.01/blib/lib/DBD/Pg.pm
/root/.cpan/build/pgsql_perl5-1.9.0/Pg.pm
/root/.cpan/build/pgsql_perl5-1.9.0/blib/lib/Pg.pm
/usr/lib/perl5/site_perl/5.6.0/i386-linux/DBD/Pg.pm
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Pg.pm
/usr/lib/perl5/site_perl/5.6.0/i386-linux/DBD-Pg-0.95/Pg.pm
/usr/lib/perl5/site_perl/5.6.0/i386-linux/DBD-Pg-0.95/blib/lib/DBD/Pg.pm
/usr/include/pgsql/Pg.pm


and perl -v says:

This is perl, v5.6.1 built for i686-linux

Then:

[root@euro oscar]# cd /usr/lib/perl5/site_perl/5.6.0/i386-linux/DBD/
[root@euro DBD]# ls
ADO.pm  ExampleP.pm  Multiplex.pm  NullP.pm  Pg.pm  Proxy.pm  Sponge.pm
[root@euro DBD]# cd ../../..
[root@euro site_perl]# ls
5.6.0/  5.6.1/  i386-linux/
[root@euro site_perl]# cd 5.6.1
[root@euro 5.6.1]# ls
Authen/  Bundle/  Convert/  LWP/  Net/  OLE/  Parse/  Spreadsheet/ 
Text/  Tie/  i386-linux/
[root@euro 5.6.1]# cd i386-linux/
[root@euro i386-linux]# ls
FCGI.pm  auto/

So the DBD directory does not exist in perl 5.6.1
I guess I had to 'un-rpm' or something the older version of perl before 
installing the newer.
How can I fix this? I just copy the missing directory?
Oops! I've just tried that! That didn't help.

Any suggestions?

Thanks,

Oscar



Thomas Good wrote:

> On Tue, 30 Oct 2001, Oscar Buijten wrote:
> 
> 
>>HI Thomas,
>>
> 
> Hey Oscar,
> 
> 
>>I have tried to re_install DBD several times and in several ways. It is 
>>there. So that doesn't seem to be the issue.
>>
> 
> Did you build DBI and DBD from the src tarball?
> 
> You see I'm wondering if you didn't install (via rpm) a mismatched version.
> I dunno if Redhat is up to 5.6.1 * or * if Lamar Owen used it when he
> built the postgresql rpms.  If memory serves you said that this all
> started when you moved to 5.6.1 so Dieter could be right that simply
> building DBI and DBD from source could fix it.  This is relatively
> painless.
> 
> If you have a simple script, say:
> ---------------------------------- cut here -----------------------------
> #!/usr/bin/perl
> use DBI;
> $dbh = DBI->connect("dbi:Pg:dbname=template1", '', '') || die "$DBI::errstr";
> $query = "select current_time";
> $sth = $dbh->prepare($query);
> $sth->execute || die "$DBI::errstr";
> $time = $sth->fetchrow_array;
> $sth->finish;
> $dbh->disconnect;
> print "\nThe time is: $time\n";
> ---------------------------------- and here -----------------------------
> 
> and you run it...it should prove interesting to see if perl complains
> about DBI.  If this works, then we need to dig deeper.
> 
> 
>>I want to go for an Pg upgrade now.
>>How do I know which rpm's are installed?
>>
> 
> rpm -qa | grep  postgresql 
> 
> 
>>Does it matter anyway? Can I just guess them as per your script?
>>How am I sure all is gone?
>>
> 
> Right.  Edit my script to match what you installed or make your own:
> rpm -qa | grep  postgresql > remove.sh
> NOTE:  you have to remove the server (base package) last or you 
> will get dependency complaints from redhat.  Or use
> rpm -e --nodeps postgresql-whatever
> 
> 
>>Will I get hassle with environment variables? Anything else?
>>
>  
> No.  This won't change.  Redhat dumps everything in
> /usr/lib or /usr/include/pgsql.
> 
> 
>>But my basic question is really: why doesn't sql-ledger work and why do 
>>all the other dbase web apps???
>>
>  
> Well, for whatever reason, DBI and DBD-Pg sometimes seem to give people
> headaches.  Maybe your other apps don't use perl?   Or they don't use
> DBI.  A version mismatch could be the culprit.  I think Dieter is right
> that you want to find out why perl is unhappy... 
> Once we get this fixed, then do an upgrade.  If necessary you leave
> out the postgresql-perl package and build the DBI drivers from source.
> 
> So, let's see if the above mentioned 'hello world' script produces
> an error.
> 
> 
>>Thanks so far!
>>
> 
> Glad to be of service.  ;-)
> 
> --------------------------------------------------------------------
>               Saint Vincent Catholic Medical Centers                
> --------------------------------------------------------------------
> Thomas Good                          tomg@ { admin | q8 } .nrnet.org
> Programmer/Analyst                              Phone:  718-818-5528 
> Behavioral Health Services                      Fax:    718-818-5056  
> Residential Services                            Mobile: 917-282-7359  
> --------------------------------------------------------------------
> /*         Rekordmeister ist nur der FC Bayern München!           */
> --------------------------------------------------------------------
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> HI Thomas,

Hey Oscar,

> I have tried to re_install DBD several times and in several ways. It is=
=20
> there. So that doesn't seem to be the issue.

Did you build DBI and DBD from the src tarball?

You see I'm wondering if you didn't install (via rpm) a mismatched version.
I dunno if Redhat is up to 5.6.1 * or * if Lamar Owen used it when he
built the postgresql rpms.  If memory serves you said that this all
started when you moved to 5.6.1 so Dieter could be right that simply
building DBI and DBD from source could fix it.  This is relatively
painless.

If you have a simple script, say:
---------------------------------- cut here -----------------------------
#!/usr/bin/perl
use DBI;
$dbh =3D DBI->connect("dbi:Pg:dbname=3Dtemplate1", '', '') || die "$DBI::er=
rstr";
$query =3D "select current_time";
$sth =3D $dbh->prepare($query);
$sth->execute || die "$DBI::errstr";
$time =3D $sth->fetchrow_array;
$sth->finish;
$dbh->disconnect;
print "\nThe time is: $time\n";
---------------------------------- and here -----------------------------

and you run it...it should prove interesting to see if perl complains
about DBI.  If this works, then we need to dig deeper.

> I want to go for an Pg upgrade now.
> How do I know which rpm's are installed?

rpm -qa | grep  postgresql=20

> Does it matter anyway? Can I just guess them as per your script?
> How am I sure all is gone?

Right.  Edit my script to match what you installed or make your own:
rpm -qa | grep  postgresql > remove.sh
NOTE:  you have to remove the server (base package) last or you=20
will get dependency complaints from redhat.  Or use
rpm -e --nodeps postgresql-whatever

> Will I get hassle with environment variables? Anything else?
=20
No.  This won't change.  Redhat dumps everything in
/usr/lib or /usr/include/pgsql.

> But my basic question is really: why doesn't sql-ledger work and why do=
=20
> all the other dbase web apps???
=20
Well, for whatever reason, DBI and DBD-Pg sometimes seem to give people
headaches.  Maybe your other apps don't use perl?   Or they don't use
DBI.  A version mismatch could be the culprit.  I think Dieter is right
that you want to find out why perl is unhappy...=20
Once we get this fixed, then do an upgrade.  If necessary you leave
out the postgresql-perl package and build the DBI drivers from source.

So, let's see if the above mentioned 'hello world' script produces
an error.

> Thanks so far!

Glad to be of service.  ;-)

--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Oscar B. <os...@el...>]

HI Thomas,

I have tried to re_install DBD several times and in several ways. It is 
there. So that doesn't seem to be the issue.
I want to go for an Pg upgrade now.
How do I know which rpm's are installed?
Does it matter anyway? Can I just guess them as per your script?

How am I sure all is gone?

Will I get hassle with environment variables? Anything else?

But my basic question is really: why doesn't sql-ledger work and why do 
all the other dbase web apps???

Thanks so far!


Oscar

Thomas Good wrote:

> On Tue, 30 Oct 2001, Thomas Good wrote:
> 
> 
>>be sure that all of your Pg stuff is the same version.  I will look around
>>here - I have a shell script to remove rpms and install the new ones.
>>
> 
>>BTW, you definitely want to use pg_dump to protect any data before you
>>make any sweeping changes as you will need to do a reload into 7.1
>>when you upgrade.  Postgres has no upgrade path for jumps in major
>>version numbers, i.e, 7.0 -> 7.1.  :-(
>>
> 
> Oscar - here is a script I used to go from 6.5 to 7.0
> If you change the version numbers, collect all of the necessary
> rpms and then run the script you should be fine.  
> Just remember to back up your data first!
> 
> #!/bin/sh
> 
> rm -ir /var/lib/pgsql/data/base
> 
> rpm -e postgresql-test-6.5.2-1
> rpm -e postgresql-jdbc-6.5.2-1
> rpm -e postgresql-odbc-6.5.2-1
> rpm -e postgresql-perl-6.5.2-1
> rpm -e postgresql-python-6.5.2-1
> rpm -e postgresql-tcl-6.5.2-1
> rpm -e postgresql-devel-6.5.2-1
> rpm -e postgresql-server-6.5.2-1
> rpm -e php-pgsql-3.0.12-6
> rpm -e postgresql-6.5.2-1
> 
> rpm -i postgresql-7.0.3-2.i386.rpm
> rpm -i postgresql-server-7.0.3-2.i386.rpm
> rpm -i postgresql-devel-7.0.3-2.i386.rpm
> rpm -i postgresql-test-7.0.3-2.i386.rpm
> rpm -i postgresql-jdbc-7.0.3-2.i386.rpm
> rpm -i postgresql-odbc-7.0.3-2.i386.rpm
> rpm -i postgresql-perl-7.0.3-2.i386.rpm
> rpm -i postgresql-python-7.0.3-2.i386.rpm
> rpm -i postgresql-tcl-7.0.3-2.i386.rpm
> rpm -i postgresql-tk-7.0.3-2.i386.rpm
> 
> /etc/rc.d/init.d/postgresql start
> 
> --------------------------------------------------------------------
>               Saint Vincent Catholic Medical Centers                
> --------------------------------------------------------------------
> Thomas Good                          tomg@ { admin | q8 } .nrnet.org
> Programmer/Analyst                              Phone:  718-818-5528 
> Behavioral Health Services                      Fax:    718-818-5056  
> Residential Services                            Mobile: 917-282-7359  
> --------------------------------------------------------------------
> /*         Rekordmeister ist nur der FC Bayern München!           */
> --------------------------------------------------------------------
> 
> 


-- 
_____________________________________________________________

Oscar Buijten

Tel: +33.4.67.57.97.45
Fax: +33.4.67.57.97.46
GSM: +33.6.20.84.15.22

Email: os...@el...

Web:   www.elbie.com

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, Dieter Simader wrote:

> It ain't broken, so why fix it.

1G versus 8k max tuple size.  That convinced me.  Initially I
didn't want to upgrade as I didn't see a need (and preferred the
old strategy for naming files in ../data/base) but I overcame
this when I had a user try to enter a record and fail due to
size limitations.  Not to mention that each release optimises
the code for performance and offers greater ansi compliance.=20
It should also be noted that template1 is backed up (as template0)
with 7.1.x - in case something bad happens to the template db.

I find myself waiting for 7.2 as I'm hoping DROP COLUMN will be
added...this is long overdue.

Anyway, 1G as a max tuple size brings Pg up to Oracle standards.
That ain't a bad thing.

--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Dieter S. <dsi...@sq...>]

recompile DBD-Pg and leave the rest alone.

It ain't broken, so why fix it.


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> Hi Thomas,
> 
> As  psql -V says:
> psql (PostgreSQL) 7.0.3
> 
> Why then not just install: postgresql-perl-7.0.3-8 RPM for i386 ??
> 
> from: 
> http://rpmfind.net/linux/RPM/redhat/7.1/i386/postgresql-perl-7.0.3-8.i386.html
> 
> This woul save me the hassle of reinstalling, pg_dumping and whatever 
> else....
> 
> Is my assumption correct??
> 
> Regards,
> 
> Oscar

Re: Upgraded to perl v5.6.1 => result: Error! No database drivers available

[Thomas G. <to...@ad...>]

On Tue, 30 Oct 2001, Oscar Buijten wrote:

> Hi Thomas,
>=20
> As  psql -V says:
> psql (PostgreSQL) 7.0.3
>=20
> Why then not just install: postgresql-perl-7.0.3-8 RPM for i386 ??
>=20
> from:=20
> http://rpmfind.net/linux/RPM/redhat/7.1/i386/postgresql-perl-7.0.3-8.i386=
=2Ehtml
>=20
> This woul save me the hassle of reinstalling, pg_dumping and whatever=20
> else....
>=20
> Is my assumption correct??

This will work but if we have to do the work why not upgrade?
7.1 sports outer joins and other new features but the most important
improvement for me (I recently upgraded) was the maximum size of a row
leapt from 8k to 1G!  This solved alot of problems for me.

Here is the upgrade path:

1.  pg_dump oscar > oscar.df  (where oscar is your db name)
2.  postgresql stop
3.  rm all the old rpms
4.  install the new ones
5.  postgresql start (it will run initdb and vacuum the new database)
6.  as the postgres user:  createuser nobody  (and whomever else you need)
7.  psql oscar < oscar.df

It is quite simple really and I will help you if you get stuck.
I think the upgrade is worth it and you won't regret knowing how to
do a dump and reload anyhow.  It is the best way to test that your
data backups are succeeding.  ;-)

The only hassle is recreating users but if you use a web interface
like sql ledger even this is no problem as the number of users is
generally limited (I have only nobody on pg and one or two on oracle.)

In any case, good luck!

--------------------------------------------------------------------
              Saint Vincent Catholic Medical Centers               =20
--------------------------------------------------------------------
Thomas Good                          tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst                              Phone:  718-818-5528=20
Behavioral Health Services                      Fax:    718-818-5056 =20
Residential Services                            Mobile: 917-282-7359 =20
--------------------------------------------------------------------
/*         Rekordmeister ist nur der FC Bayern M=FCnchen!           */
--------------------------------------------------------------------