Quoth [EMAIL PROTECTED] (slane):
> Hello all:
>
> I am upgrading a web application from postgres 7.1.2 to 7.4.3 (too long in
> coming to that point, I know).
>
> I have sifted through the history files and identified a restricted number
> of changes that potentially impact the app, a few of which I
slane <[EMAIL PROTECTED]> writes:
> Here¹s the currently most alarming, a change that is recorded for 7.2:
> CHAR(), VARCHAR() now reject strings that are too long (Peter E)
> What does this mean? Or how do I find out what it means?
If in doubt, experiment.
In 7.1:
regression=# create table foo(
Hello all:
I am upgrading a web application from postgres 7.1.2 to 7.4.3 (too long in
coming to that point, I know).
I have sifted through the history files and identified a restricted number
of changes that potentially impact the app, a few of which I don¹t
understand.
Here¹s the currently most
I set the tcp_ip=true in postgresql.conf file. Isn't that the same thing while starting up postmaster with -i. Becasue i am starting up the server using pg_ctl .
Regards
Andrew Janian <[EMAIL PROTECTED]> wrote:
Are you using -i option when you start Postgres? If not, it will not allow remo
I'd
not call it a "distributed database". It's simply replication of data from
one database to another, & SlonyI will do that for you in Postgres.
Down loaded it & the documentation form the Postgres web
site.
Dick GouletSenior Oracle DBAOracle Certified 8i
DBA
-Original Message
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> MPaule Torre wrote:
>> I have a red hat ent.3 operationg system. It has been delivered with
>> postgresql v7.3.6-1
> I'd like to know why RH still deliver 7.3.x after almost one year
> with the 7.4 around.
Because their policy is "no breakage for the
Hi,
I'm trying to use the psql application to execute pg_dump to backup a
database named test_db. When I run psql interactively, as user dba
connected to database test_db, and enter the command
\! pg_dump -U dba -f /backup/adp_test_db.bak -F c test_db
The command executes with no error and the
MPaule Torre wrote:
Hello everybody
I have a red hat ent.3 operationg system. It has been delivered with
postgresql v7.3.6-1
I'd like to know why RH still deliver 7.3.x after almost one year
with the 7.4 around.
Regards
Gaetano Mendola
---(end of broadcast)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Usually the RPM's work fine if they're build for that version of operating
system.
What I tend to do is not trust RPM to do the update correctly (particularly
with postgres).
So normally for an upgrade I:
pg_dumpall > backup.dump
shut down the postm
Are
you using -i option when you start Postgres? If not, it will not allow
remote requests even if you have the ACL set correctly.
Andrew
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Mohammad Tanvir
HudaSent: Thursday, August 12, 2004 1
Hello
i have made some entry in pg_hba.conf so that it can accept call from other computers.
But it still giving me the same error .
Can anyone pls tell me what is wrong with that
Regards
Mohammad Mohammad Tanvir Huda <[EMAIL PROTECTED]> wrote:
Hello All
Thanks for your reply.
i w
Hello everybody
I have a red hat ent.3 operationg system. It has been delivered with
postgresql v7.3.6-1
I would like to use a new stable version : v7.4.3
(server on linux and an ontother PC under windows 2000 to test and develop
: with cygwin => v7.4.3 or v7.4.2 available)
Do you have any info
Hi Tom,
Just re-installed a new version of Postgres 7.3.4 on a *clean* version
of Mandrake 9.2, which seemed to work well. The reference to the
xlateSqlType symbol is gone from plpgsql.so.
All postgres packages installed came from the original Mandrake 9.2 CD.
After a little search plpgsql.so
13 matches
Mail list logo
