On Fri, 29 Sep 2000, Adam Lang wrote:
> I know you had to add the module for mysql for PHP 3, but I thought PHP 4
> mysql was a native part.
>
> I compiled php 4 ad specifically asked for postgres support, while
> compiling, it mentioned how mysql APIs were being added any way (even
> though
On 29 Sep 2000, Trond Eivind Glomsrød wrote:
> > But claiming that you can't upgrade is painting over what might rather be
> > a deficiency in the RPM mechanism, ISTM. Why can't you have a spec file
> > like this:
> >
> > %preupgrade
> > pg_dumpall >somewhere
>
>
> 1) You don't know that post
The mailing address in my address book (which is what I generally use):
[EMAIL PROTECTED]
The daily digests I get have the following email address at the top:
[EMAIL PROTECTED]
Both seem to work for me.
- Tim
Richard Brown wrote:
>
>
"Keith L. Musser" <[EMAIL PROTECTED]> writes:
> Gunnar,
>
> Your new JDBC driver (postgresql.jar, 29-Sept-2000, 14:47, 187K) caused
> the following error.
>
>
> SELECT host, port FROM Servers WHERE PID=1;
> Bad Integer int4
> at org.postgresql.jdbc2.ResultSet.getInt(ResultSet.java:261)
> at o
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> But claiming that you can't upgrade is painting over what might rather be
> a deficiency in the RPM mechanism, ISTM. Why can't you have a spec file
> like this:
>
> %preupgrade
> pg_dumpall >somewhere
1) You don't know that postgresql is running.
Trond Eivind Glomsrød writes:
> Incidentally, you can dump data from a database. You can also insert
> data into a database. If you do this before and after upgrading,
> you'll hopefully have the same data in the database.
If there's a problem with pg_dump then pg_dump needs to be fixed, and
inc
On Fri, Sep 29, 2000 at 11:41:51AM -0500, Jeff Hoffmann wrote:
> Bryan White wrote:
> >
> > I am thinking that
> > instead I will need to pipe pg_dumps output into gzip thus avoiding the
> > creation of a file of that size.
>
> sure, i do it all the time. unfortunately, i've had it happen a few
Bryan White wrote:
>
> I am thinking that
> instead I will need to pipe pg_dumps output into gzip thus avoiding the
> creation of a file of that size.
>
sure, i do it all the time. unfortunately, i've had it happen a few
times where even gzipping a database dump goes over 2GB, which is a real
I know you had to add the module for mysql for PHP 3, but I thought PHP 4
mysql was a native part.
I compiled php 4 ad specifically asked for postgres support, while
compiling, it mentioned how mysql APIs were being added any way (even
though
I did not tell it to).
I'm sure it can be extra
Tom Lane wrote:
>
> "Efrain Caro" <[EMAIL PROTECTED]> writes:
> > Forgive my ignorance. What is this no-upgrade policy issue about?
>
> It's not a "policy", it's just a problem: you usually can't update to
> a new major Postgres release without doing dump/initdb/reload.
The 'policy' is the lack
Well, I treat upgrading RedHat like I treat upgrading any OS... clean
install.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
- Original Message -
From: "Jeff Hoffmann" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, September 29, 2000 10:45 AM
Subject: Re: [GENER
> My current backups made with pg_dump are currently 1.3GB. I am wondering
> what kind of headaches I will have to deal with once they exceed 2GB.
>
> What will happen with pg_dump on a Linux 2.2.14 i386 kernel when the
output
> exceeds 2GB?
There are some ways around it if your program suppor
On Fri, Sep 29, 2000 at 12:15:26PM -0400, Bryan White wrote:
> My current backups made with pg_dump are currently 1.3GB. I am wondering
> what kind of headaches I will have to deal with once they exceed 2GB.
>
> What will happen with pg_dump on a Linux 2.2.14 i386 kernel when the output
> exceed
My current backups made with pg_dump are currently 1.3GB. I am wondering
what kind of headaches I will have to deal with once they exceed 2GB.
What will happen with pg_dump on a Linux 2.2.14 i386 kernel when the output
exceeds 2GB?
Currently the dump file is later fed to a 'tar cvfz'. I am thin
"Keith L. Musser" <[EMAIL PROTECTED]> writes:
> Gunnar,
>
> Your new JDBC driver (postgresql.jar, 29-Sept-2000, 14:47, 187K) caused
> the following error.
>
Thanks, I will look into the problem. The regression tests that Peter Mount
talking about would have been nice to have to catch things li
On Fri, 29 Sep 2000, Efrain Caro wrote:
> So we can say that we can upgrade, at least in theory, but that's not the
> official policy?
Well, I don't know about 'policy', but yes, you can upgrade PostgreSQL,
you just need to dump your data first (which you should do anyway to
backup -- never upgr
Gunnar,
Your new JDBC driver (postgresql.jar, 29-Sept-2000, 14:47, 187K) caused
the following error.
Using these tables...
>>> CREATE TABLE servers ( pid INT4 PRIMARY KEY, tableid INT2, host
TEXT, port INT4);
>>> CREATE TA
So we can say that we can upgrade, at least in theory, but that's not the
official policy?
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Trond Eivind Glomsrød" <[EMAIL PROTECTED]>
Cc: "Efrain Caro" <[EMAIL PROTECTED]>; "Jeff Hoffmann"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: F
"Efrain Caro" <[EMAIL PROTECTED]> writes:
> Forgive my ignorance. What is this no-upgrade policy issue about?
It's not a "policy", it's just a problem: you usually can't update to
a new major Postgres release without doing dump/initdb/reload.
regards, tom lane
On 29 Sep 2000, Trond Eivind Glomsrød wrote:
> That you can't upgrade postgresql from e.g. 6.5 to 7.0 or from 7.0 to
> 7.1
>
> Incidentally, you can dump data from a database. You can also insert
> data into a database. If you do this before and after upgrading,
> you'll hopefully have the same
"Darrin Ladd" <[EMAIL PROTECTED]> writes:
> I have Postgres 7.0.2 installed on an Alpha running Red Hat Linux 6.2. The
> table is truncated and loaded with approximately 40,000 records per day.
> The load is done by performing a COPY FROM. The first time it was ever
> loaded, the load was done u
"Efrain Caro" <[EMAIL PROTECTED]> writes:
> Forgive my ignorance. What is this no-upgrade policy issue about?
That you can't upgrade postgresql from e.g. 6.5 to 7.0 or from 7.0 to
7.1
Incidentally, you can dump data from a database. You can also insert
data into a database. If you do this befo
Forgive my ignorance. What is this no-upgrade policy issue about?
Jeff Hoffmann <[EMAIL PROTECTED]> writes:
> > >>> "Alfredo" <[EMAIL PROTECTED]> 09/29/00 12:28PM >>>
> > I heard that MySQL is included in RH 7 instead of PgSQL. Is this true?
if
> > yes, anybody know why?
>
> i think the thing is
Jeff Hoffmann <[EMAIL PROTECTED]> writes:
> > >>> "Alfredo" <[EMAIL PROTECTED]> 09/29/00 12:28PM >>>
> > I heard that MySQL is included in RH 7 instead of PgSQL. Is this true? if
> > yes, anybody know why?
>
> i think the thing is that they added mysql because it's now GPL'd -- it
> wasn't in th
Trond Eivind Glomsrød wrote:
> "Alfredo" <[EMAIL PROTECTED]> writes:
> > I heard that MySQL is included in RH 7 instead of PgSQL. Is this
> > true?
> No. Postgresql is included, and is the one installed when choosing
> "SQL Server" under the custom category. To get MySQL, you would have
> to i
I have Postgres 7.0.2 installed on an Alpha running Red Hat Linux 6.2. The
table is truncated and loaded with approximately 40,000 records per day.
The load is done by performing a COPY FROM. The first time it was ever
loaded, the load was done using insert statements, with autocommit on and
the
"Adam Lang" <[EMAIL PROTECTED]> writes:
> Not to mention the fact that PHP 4 installs with MySQL support native.
While we have a MySQL module for PHP, we also have a pgsql module.
> If RedHat did do MySQL by default, technically Apache, PHP, and MySQL would
> be a pretty straightforward Web Se
> Why not just have the application do both? You won't get the integrity
> of transactions, but mysql doesn't give you that anyway... ;-)
>
> Pardon me if I misunderstood what you were trying to do.
Right now I'm just trying to do some preliminary planning,
(hell, V1.0 isn't release JUST yet (
> >>> "Alfredo" <[EMAIL PROTECTED]> 09/29/00 12:28PM >>>
> I heard that MySQL is included in RH 7 instead of PgSQL. Is this true? if
> yes, anybody know why?
i think the thing is that they added mysql because it's now GPL'd -- it
wasn't in there before because it wasn't really "free" software.
p
Not to mention the fact that PHP 4 installs with MySQL support native.
If RedHat did do MySQL by default, technically Apache, PHP, and MySQL would
be a pretty straightforward Web Serving bundle.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
- Original Message -
From: "Tro
"Alfredo" <[EMAIL PROTECTED]> writes:
> I heard that MySQL is included in RH 7 instead of PgSQL. Is this
> true?
No. Postgresql is included, and is the one installed when choosing
"SQL Server" under the custom category. To get MySQL, you would have
to install them manually afterwards, select "e
> I tried to run the Postgres.exe file but it complained about the version
> found being 7.0 and it requiring version 7.0 - huh?
Look for the files called VERSION in the data directory and its descendants
and convert them from windows text format to unix text format.
32 matches
Mail list logo
