DuSTiN KRySaK wrote:
Hi there - just learning redhat, and I need to learn a SQL - now I was
wondering what the diff was between Mysql VS postgreSQL? Is one easier for a
beginner than the other? One more stable? One play nicer with web pages
(that will be my use for it).
You probably won't
On Mon, 10 Mar 2003, DuSTiN KRySaK wrote:
> wondering what the diff was between Mysql VS postgreSQL? Is one easier
They are similar but different. The best thing to do is to determine what
functionality your relational database needs, and then pick the one that
comes closest to meeting th
Hi there - just learning redhat, and I need to learn a SQL - now I was
wondering what the diff was between Mysql VS postgreSQL? Is one easier for a
beginner than the other? One more stable? One play nicer with web pages
(that will be my use for it).
Thanks!
d
--
redhat-list mailing list
y not that scary ;)
http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=backup.html
/B
- Original Message -
From: "Juan Nin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 11:19
Subject: Re: MySQL vs. PostgreSQL
> F
: MySQL vs. PostgreSQL
I just shut down mysql and copy the directory to a folder that is backed up
on the regular backup so the database down time is about a minute. The only
problem with this is if you have set up your user access rights in the mysql
database which is the one used by mysql to grant
Ryurick M. Hristev
Sent: Thursday, February 27, 2003 5:57 PM
To: [EMAIL PROTECTED]
Subject: Re: MySQL vs. PostgreSQL
On Wed, 26 Feb 2003, Joe Giles wrote:
> Question about backing up...
>
> Sorry if this is not on the lines of what you guys are talking about,
> but I set up MySQL and I
/maintenance.sql -U $DB_USER $DATABASE
- Original Message -
From: "Ryurick M. Hristev" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 27, 2003 14:56
Subject: Re: MySQL vs. PostgreSQL
> On Wed, 26 Feb 2003, Joe Giles wrote:
>
> > Questio
On Wed, 26 Feb 2003, Joe Giles wrote:
> Question about backing up...
>
> Sorry if this is not on the lines of what you guys are talking about,
> but I set up MySQL and I sym link the database from one file system to
> another for redundancy purposes. So, when I upgrade, I just break the
> link an
I am using MySQL. It is getting about about 3 million records a month
added to it. It does not fail under the load, but slowes down to the
point where it is not usable. What we have to do is move the data out of
the active table into another table.
david
On Wed, 26 Feb 2003, Juan Nin wrote:
>
On Jue 27 Feb 2003 02:32, Joe Giles wrote:
> Question about backing up...
>
> Sorry if this is not on the lines of what you guys are talking about,
> but I set up MySQL and I sym link the database from one file system to
> another for redundancy purposes. So, when I upgrade, I just break the
> link
On Mié 26 Feb 2003 18:58, Ryurick M. Hristev wrote:
>
> > That's true with all the database systems I have used (Informix, Oracle
> > and PostgreSQL).
> > It has to do with how diferent versions handly the database files, and
> > how it changes. Any way, you don't have to do a dump-restore with pa
Well, I stated that for redundancy I created sym links. That isn't the
proper wording I should have used. What I meant to say was I created sym
links from one file system to another for space reasons. I ran out of
space on the /var part. so I linked the databases to another fs. Sorry
for the misund
Joe Giles said:
> Question about backing up...
>
> Sorry if this is not on the lines of what you guys are talking about, but
> I set up MySQL and I sym link the database from one file system to another
> for redundancy purposes. So, when I upgrade, I just break the link and
> upgrade, then re link.
Question about backing up...
Sorry if this is not on the lines of what you guys are talking about,
but I set up MySQL and I sym link the database from one file system to
another for redundancy purposes. So, when I upgrade, I just break the
link and upgrade, then re link. It has worked so far (well
On Wed, 26 Feb 2003, Martin Marques wrote:
> On Mié 26 Feb 2003 16:19, Juan Nin wrote:
> > From: "David Busby" <[EMAIL PROTECTED]>
[...]
> > I've heared that upgrading is more painfull with PostgreSQL, since you have
> > to dump the databases and restore them again after the upgrade
[...]
> Th
Juan Nin wrote:
I've heared that upgrading is more painfull with PostgreSQL, since you have
to dump the databases and restore them again after the upgrade
Dump and rebuild is an easy and reliable way to preserve your data through
db engine updates. Are you saying that if the binary formats were
c
From: "David Busby" <[EMAIL PROTECTED]>
> Juan,
> After performing the Dump/Import for the upgrade once it's cake.
There
> are two utilities that you can use
> pg_dump
> to dump data
> psql < [file]
> to restore
> so before I upgrade I simply
> pg_dump [options] [dbname]
> to my ar
amp;file=backup.html
/B
- Original Message -
From: "Juan Nin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 11:19
Subject: Re: MySQL vs. PostgreSQL
> From: "David Busby" <[EMAIL PROTECTED]>
>
> > I'
From: "Stefan Neufeind" <[EMAIL PROTECTED]>
> Well yes and know to the use / not use MySQL-question. I wouldn't
> rate the university-use "mission critical". It runs good, that's what
> I hear from many people. And it's stablizing more and more. Got a
> bugfix-newsletter yesterday which only in
> I've heared that upgrading is more painfull with PostgreSQL,
> since you have
> to dump the databases and restore them again after the upgrade
Yes it's true you need to dump the databases and restore them, but I
disagree that it's painful.
It's fairly quick and easy with `pg_dumpall`. In fact y
On 26 Feb 2003 at 11:28, nate wrote:
> Juan Nin said:
>
> > but I've heared that the new MySQL 4.x branch changes this a bit,
> > and that from MySQL 4.1 there are nested queries support, etc
>
> I most certainly would reccomend AGAINST using mysql 4.x unless your
> app has a long development ti
> I most certainly would reccomend AGAINST using mysql 4.x unless your
> app has a long development time to give mysql 4.x time to stabilize(I
> would not use it for probably at least a year). It still isn't "final"
> according to mysql.com. And even after it is I would not deploy it
> immediately.
I have to preface this by saying that I haven't personally used
Postgres for anything...
I use MySQL for database-driven websites and a db-driven chat system
that I am toying with. While the sites I have running are low-volume,
I would note that I ran ApacheBench against one of them to see ho
Juan Nin said:
> but I've heared that the new MySQL 4.x branch changes this a bit, and that
> from MySQL 4.1 there are nested queries support, etc
I most certainly would reccomend AGAINST using mysql 4.x unless your
app has a long development time to give mysql 4.x time to stabilize(I
would not u
Personally speaking I must tell you that I like MySQL very much
because of its compactness (in the 3.x-releases). But at some points
you're right, it wasn't the best database-solution to choose because
of it's features - but I was able to "emulate" a lot through php-
scripts.
The 4.x-branch chan
From: "David Busby" <[EMAIL PROTECTED]>
> I've always loved PostgreSQL I use it for large and small projects, with
> some real nasty/ugly nested queries. It still performs great even under
> some heavy load. Make sure you get a real (real) fast HDD (LVD SCSI 15K
> RPM), the slower the drive the
.
/B
- Original Message -
From: "Juan Nin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 11:07
Subject: MySQL vs. PostgreSQL
> Hi,
>
> I'm about to make a kind of yahoogroups in PHP. It's for a University, so
it
> w
Hi,
I'm about to make a kind of yahoogroups in PHP. It's for a University, so it
will be used a lot.
I'm considering using either MySQL or PostgreSQL...
Which one would you recommend for this project?
I've always heared that PostgreSQL is better for big databases with lots of
records, where data
28 matches
Mail list logo
