[ADMIN] Upgrading O/S requires Postgres re-build?

2006-02-09 Thread Tomeh, Husam
Server running Postgres 7.4.5 with: Red Hat Enterprise Linux AS release 3.90 (Nahant) Linux 2.6.9-1.648_ELsmp #1 SMP Tue Oct 26 12:24:18 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux I want to upgrade the O/S to: Red Hat Enterprise Linux AS release 4 (Nahant) Linux 2.6.9-5.ELsmp #1 SMP Wed

Re: [ADMIN] Postgresql 8.0 or 8.1 vs. latest Red Hat RPM

2006-02-09 Thread Dominik Składanowski
Hello list, Bradley Kieser wrote: > I would always use the latest stable release from the PG project for > four reasons: > a) Databases are notoriously difficult to upgrade once they are in [ ... ] > > b) The dev team just keeps on making this wonderful DB better. Every > release is a gem and we

Re: [ADMIN] Postgresql 8.0 or 8.1 vs. latest Red Hat RPM

2006-02-09 Thread Devrim GUNDUZ
Hi, On Thu, 2006-02-09 at 23:58 +0100, Dominik Składanowski wrote: > And now, if I need PostgreSQL as a base for PHP aplication? Package > php-pgsql-4.3.9-3.9.rpm (distributed with CentOS/RHEL) will be works > with PostgreSQL 8.1.2? No. You'll need our compat RPM: http://developer.postgresql.or

Re: [ADMIN] Upgrading O/S requires Postgres re-build?

2006-02-09 Thread Chris Browne
[EMAIL PROTECTED] ("Tomeh, Husam") writes: > Server running Postgres 7.4.5 with: > > Red Hat Enterprise Linux AS release 3.90 (Nahant) > Linux 2.6.9-1.648_ELsmp #1 SMP Tue Oct 26 12:24:18 EDT 2004 x86_64 > x86_64 x86_64 GNU/Linux > > I want to upgrade the O/S to: > > Red Hat Enterprise Linux

Re: [ADMIN] Postgresql 8.0 or 8.1 vs. latest Red Hat RPM

2006-02-09 Thread Dominik Składanowski
> > And now, if I need PostgreSQL as a base for PHP aplication? Package > > php-pgsql-4.3.9-3.9.rpm (distributed with CentOS/RHEL) will be works > > with PostgreSQL 8.1.2? > > No. You'll need our compat RPM: > > http://developer.postgresql.org/~devrim/rpms/compat/ > > There are 2 RPMs for 32 and 64

[ADMIN] Need query parameter in logs

2006-02-09 Thread Robert Perry
I am trying to help debug a application that is deployed in the field. I suspect that it is sending some unexpected values to some stored procs, but the logs look very much like: Feb 9 14:29:26 localhost postgres[3138]: [122-1] LOG: statement: Select * from game_state_set_disqualified( $1,