Hi Tarun,
I think you are trying to compare a Apple with a Water Melon. But any
case if you are really facing a real time scenario, please make it clear. what exactly
the application you are running and how many concurrent user you are expecting to be
there as concurrency is a major factor which can cause ample amount of problems for
the DBA. I make sure that I would be able to solve all your queries.
Regards,
Gurpreet Singh Sachdeva
-----Original Message-----
From: Tarun Upadhyay [mailto:[EMAIL PROTECTED]
Sent: Fri 10/10/2003 9:50 PM
To: 'The Linux-Delhi mailing list'
Cc:
Subject: [ilugd] Postgres vs oracle
We have a customer application on oracle.
They want to crate a "small footprint" version of it to be sold at a cheaper
price.
I want to suggest that Postgres could be the right choice of database for
that as it is close to oracle in its sql syntax and hence porting should be
simpler.
Can anybody guide me on what kind of pitfalls we could run into by choosing
Postgres. The database is not very large but is much larger than what goes
for "database" in mysql discussions (about 1 GB of data, 100 tables with
about 10-50 MB added every day)?
In particular, I would be interested in hearing from people who have run
moderately large databases on postgres and how fast they found it.
I have heard that it is possible to now provide replication and fail over
with postgres. Has anybody tried it?
Tarun
_______________________________________________
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
_______________________________________________
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
