By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,708 Members | 2,055 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,708 IT Pros & Developers. It's quick & easy.

Is Win32 port good for operational use?

P: n/a
Hi,

I know we will be using at our own risk, I have read the
"experimental" warnings, but still PostgreSQL is a very attractive
RDBMS for the Windows application we are developing. Most customers
will want a simple single-machine version, where the program will be
storing its data in a local database without the user knowing much
about it. Some customers will want a central database and will
probably be given the option to choose between PostgreSQL and Oracle.
The problem is to choose the RDBMS for the single-machine, single-user
version.

What if we have crashes or other critical bugs? Should we expect
reasonable support from the developers in such cases? Is the number
of Win32 developers decent? I mean, the Win32 project is not, I hope,
supported by one or two key people and would go down if they decided
to become sailors instead? :-)

Needless to say, the developers will have all kind of help from us in
tracking down important bugs, even access to our machines if
necessary.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I've been using the Win32 port of PostgreSQL for several months now on a
pre-production test machine without much difficulty, in in my
environment I've had more trouble with MySQL in general than PostgreSQL
on Windows I'd recommend installing the beta and trying it out.
Depending on the features you wish to utilize it sounds like SQLite may
also be an option, it is a light-weight embeddable SQL solution, it uses
a single file to store the database in making end user backups much
easier and does not require an additional process on the client OS since
it is embedded in the application.

Jason

Antonios Christofides wrote:
Hi,

I know we will be using at our own risk, I have read the
"experimental" warnings, but still PostgreSQL is a very attractive
RDBMS for the Windows application we are developing. Most customers
will want a simple single-machine version, where the program will be
storing its data in a local database without the user knowing much
about it. Some customers will want a central database and will
probably be given the option to choose between PostgreSQL and Oracle.
The problem is to choose the RDBMS for the single-machine, single-user
version.

What if we have crashes or other critical bugs? Should we expect
reasonable support from the developers in such cases? Is the number
of Win32 developers decent? I mean, the Win32 project is not, I hope,
supported by one or two key people and would go down if they decided
to become sailors instead? :-)

Needless to say, the developers will have all kind of help from us in
tracking down important bugs, even access to our machines if
necessary.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.