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

Re: Stumped by a version conflict.

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: bluestar43(at)gmail(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Stumped by a version conflict.
Date: 2010-07-17 00:48:42
Message-ID: AANLkTiniwbSrCHiXF2pRrq2aZ6HdcrT1efH-b_oK20TO@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Fri, Jul 16, 2010 at 6:08 PM, Patric Michael <bluestar43(at)gmail(dot)com> wrote:
> Thank you Tom, and I do agree in theory, but I am still unconvinced that
> something else isnt amiss because I do recall having to rewrite the web
> scripts which access the database, after I upgraded.  Seems there was a
> change where an empty field no longer returned a zero but a null (or vice
> versa) when pg_python performed a SELECT * statement.  It is that little bit
> that makes me wonder if is somehow still possible that the database was in
> fact initialized with 8.1 despite reporting 7.4...

So what does

sudo locate postgresql.conf

say?

In response to

Responses

pgsql-admin by date

Next:From: Patric MichaelDate: 2010-07-17 05:10:54
Subject: Re: Stumped by a version conflict.
Previous:From: Stephen FrostDate: 2010-07-17 00:10:53
Subject: Re: Stumped by a version conflict.

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