|
|
|
|
|
|
| Author |
Message |
Chris Travers *nix forums addict
Joined: 08 Mar 2005
Posts: 96
|
Posted: Fri Mar 11, 2005 8:11 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Tope Akinniyi wrote:
| Quote: | Hi all,
In my country Nigeria (and even African continent), we do not eat what
the western world eat. We wear different styles of cloths. In the same
vein, our computerisation culture is different.
|
Having lived in Indonesia, I can sympathize with your situation. It is
not just Africa, but most of the developing world.
| Quote: |
I must submit that computers became popular in Nigeria by Windows
desktop system. While the western world were exposed to *NIX from the
beginning, we were introduced to computing via DOS and later Windows.
That is our IT antecedent and culture. People use database engines
such as Oracle, Firebird, Sybase, mySQL, etc on Windows here and they
manage them and survive. If because you want to recommend PostgreSQL,
you insist on Non-Windows OS, the first question clients ask you is
why is your own different? Why must I switch from Windows to *NIX
because of your PostgreSQL? You might end up not succeeding in that
bid. And we are used to the blue screen (crashes) and each IT house in
Nigeria has gone the extra mile to ensure the safety of the operations
of its clients. Everyone is a product of his environment,
peculiarities and experiences.
|
If you want a reasonable open source RDBMS for production use on
Wondows, I would suggest that you use Firebird. However if Windows is
not the selling point, consider the following:
1) You may be able to get extra use out of older systems by installing
Linux and PostgreSQL. This may perform better than Windows and Firebird
as long as you don't need a GUI. This may be more reliable than Windows
especially if you can't afford high-end hardware (ECC RAM, SCSI drives,
etc) for your production servers anyway.
2) The PL's available for PostgreSQL add a lot of flexability.
| Quote: |
As an IT organisation that wants to stay in business you need to give
to people what they wants. I think that is the basis of service. I
have some deployments of PostgreSQL on Windows servers. I must admit
that we have not had any problems so far.
|
The glory of open source is that people will do what they want with
it. PostgreSQL for Windows is not really something I would run a large
production database on at the moment. However, open source tools tend
to develop in strange ways. I am sure that as PostgreSQL on Windows
becomes more popular, the issues will get worked out as much as possible.
| Quote: | Notwithstanding, due efforts must be made to protect your clients'
operations whether you use Windows or Posix. In that regards, I
thought of reducing the risk factor by implementing replication on
some of the servers.
|
Command Prompt's solution works on Windows. Slony will require some
porting, but if this is important, you can hire a programmer to help
with the porting Otherwise you can wait for someone else to do it.
| Quote: |
I sought Windows replication tool for and could not get. I checked
PgFoundry and the one there put a banner and said NOT FOR WINDOWS.
Then I said is this PostgreSQL for Windows a joke? That prompted
my post - IS POSTGRESQL FOR LINUX ONLY?
|
Check the archives about Slony-I and Windows. Maybe ask the developers
how much work it would be to port it. If labor is inexpensive in
Nigeria, maybe you can hire a programmer to do it.
| Quote: | Now, as the CEO of an IT organisation, I want to draft my final
blueprint on PostgreSQL. I need your advice on this.
1. If I can manage it, can I continue to use PostgreSQL on Windows and
watch as it evolves? I recognise the points certain respondents made
on earlier; which was PostgreSQL on Windows is still a baby boy, do
not expect it to walk like a man or expect it to possess the features
of a man.
|
Ok, maybe others can provide more refined estimates, but....
I expect that it will be 1-2 years before PostgreSQL on Windows is
mature enough for higher-load purposes. You can however help by using
it, and communicating your experiences with programmers. If this is not
enough, you can even pay someone to fix things for you. These are
selling points of open source software.
| Quote: |
2. This response is alarming:
Tom Lane wrote in digest V1.5092:
We are supporting Windows as a Postgres platform for the benefit of
developers who want to
do testing on their laptops (and for reasons best known to themselves
feel a need to run >Windows on their laptops).
a. Who are the 'we' Tom is talking about?
b. Is he speaking for PostgreSQL Developers and the entire PostgreSQL
community?
|
As much as I don't like to speak for others, I read this as saying
something like:
"We (the core developers) began work on the Windows port because we
wanted to support developers running PostgreSQL on their systems."
| Quote: | c. Does this mean that PostgreSQL for Windows is just a toy or model -
Oh do not take it serious? Or is the Windows version by design a
miniature of the *NIX version, lacking the requisite mechanism of a
reliable database?
|
I think the core team takes all aspects of PostgreSQL very seriously.
Part of the problem is that they are so serious about it that they don't
want problems in Windows to smear the name of PostgreSQL. So comments
like Windows being unsuitable for any RDBMS use applies to MS SQL and
Firebird as PostgreSQL. But that doesn't mean that people won't do the
best that they can to make it work.
| Quote: | d. And does that mean the developers can decide to withdraw
development and support for the Windows version anytime they so wish?
|
Individual developers can decide whatever they want. However, as long
as Windows/PostgreSQL is popular, it will be supported regardless of
whatever the core team wants to do. This is because the community has
access to the source code and that the community will include a large
number of software developers. But no, I don't see the core team
deciding to remove supported platforms any time soon. We are not a
centralized commercial enterprise like MySQL, so whatever the community
really wants, they will eventually get.
| Quote: | I am not against Linux or any Posix for any reason. In fact one of my
two office servers run Mandrake Linux. But I am grateful that
PostgreSQL recognises the fact that we all can and will not be in the
same boat. So it is good to support many boats.
Tom lane's post is worrisome to me. It bothers on consistency. Would
PostgreSQL be consistent for Windows? If not, I think at this stage I
can easily roll back and migrate my clients back to other Windows
Database system where I feel I will be secured for some time to come
as using PostgreSQL does not affect much of my operations. I am just
expanding my varieties.
|
Why should it matter? What will happen is that PostgreSQL on Windows
will become commonly used in both development and production
environments. It won't be fast like on Linux because of fork() overhead
but it will be supported as long as the community wants it.
| Quote: |
I think managing PostgreSQL on OS I desire should be my own duty. The
point is that PostgreSQL can be available for what I choose to use it
for and where I choose to use it. Managing failure points of my OS
should be left to my technical expertise. Well if I can get some
support from some sources, fine.
I do not seem to be comfortable with this "Windows will spoil
PostgreSQL reputation position" as posted by Schroeder. Is PostgreSQL
the only database engine running on Windows? There are million of
licences of Oracle, mySQL, Sybase, etc for Windows servers. The
company that uses them are up and running; not as if only
organisations running DB on Posix are existing. Who blames mySQL or
Oracle when it crashes on Windows OS? If PostgreSQL cannot thrive
where others thrive, it will be quite unfortunate. You cannot shut
yourself indoors because you anticipate a rainfall (that might not
come). What would be the empirical basis for our judgement if
PostgreSQL is not used on Windows? Crashing MS Office on Windows is a
different situation from what you would get running PostgreSQL. I do
often witness many utility *NIX applications do crash on our Mandrake
server, but not PostgreSQL crashing.
|
As I said, the core team takes the security of your data very
seriously. Note that this does not mean that it will nto be supported,
but just that people don't think you should consider doing this.
I hope this response is helpful.
Best Wishes,
Chris Travers
Metatron Technology Consulting |
|
| Back to top |
|
 |
tony *nix forums addict
Joined: 08 Mar 2005
Posts: 81
|
Posted: Fri Mar 11, 2005 3:53 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Le vendredi 11 mars 2005 à 17:41 +0100, Magnus Hagander a écrit :
| Quote: | Do *not* do this with a production database.
Vmware does *not* correctly handle fsync()s (or O_SYNC or any of
those) thruogh to disk. If your host PC crashes, your database will
almost certainly be corrupted. fsync() on the client just
puts it in
the RAM cache on the host. Not even in the write cache on
the disk/raid.
....snip
It's possible this works fine if you use direct disk access in vmware
(giving the session a native disk to access), but I haven't tried that.
|
OK! I understand your worries now. I always do this because initial
reading through the different disk modes when 3.0 came out made my hair
stand on end. The speed and size of disks today means that each virtual
machine can treat a part of the disk as its own as far as I'm concerned.
The other disk modes always seemed strange to me - maybe they have uses
for others... When I am in my virtual machine I like to see the HD diode
go on each time I do a save, improves my tan =:-D
| Quote: | After some looking around (and with some hints from Dave Page) for my
own needs of virtualising linux-on-linux, I've moved to linux-vservers.
While it doesn't virtualise everything, it's good enough for me. I
suggest you at least look at it before going down the vmware path - it's
also free software unlike vmware.
|
Looked at that. It requires heavy guru voodoo magic at host OS install
time. VMware (I already own the licence I was going to use) can be
installed on a machine that is up and running.
Thanks
Tony
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly |
|
| Back to top |
|
 |
Magnus Hagander *nix forums Guru Wannabe
Joined: 06 Mar 2005
Posts: 158
|
Posted: Fri Mar 11, 2005 3:41 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
| Quote: | Do *not* do this with a production database.
Vmware does *not* correctly handle fsync()s (or O_SYNC or any of
those) thruogh to disk. If your host PC crashes, your database will
almost certainly be corrupted. fsync() on the client just
puts it in
the RAM cache on the host. Not even in the write cache on
the disk/raid.
Putting Windows NT inside a virtual machine (VMware
workstation) solved all hardware stability problems in my
case. NT would only crash if we forgot to reboot every 45
days or so... The Linux host had a 9 month uptime at one point.
If you could be more explicit as to why VMware client does
not write to disk I would much appreciate. I was thinking of
virtualising a couple of servers (Linux client on Linux host). TIA
|
PostgreSQL relies on fsync() putting your data all the way through to
the disc. It must *not* stay in cache memory, because then you can lose
transactions. If write ordering is also lost (which is likely in this
case), you can get a corrupt database.
In the tests I've been running on vmware, a fsync() in the guest OS will
flush it out of the guest OSs buffer, but the data will stay in the host
OS buffers.
This means that you may be hosed if your host OS crashes. It should
survive a *guest* OS crash without problems.
I haven't had any actual crashes on this, but there is plenty of
evidence that syncing doesn't go all the way through (see my other mail)
at least with Windows as the host OS. Which means you are basically
running with write-cache enabled all the time with no way to turn it
off, and some reading of the pg lists should tell you how bad that is.
It's possible this works fine if you use direct disk access in vmware
(giving the session a native disk to access), but I haven't tried that.
After some looking around (and with some hints from Dave Page) for my
own needs of virtualising linux-on-linux, I've moved to linux-vservers.
While it doesn't virtualise everything, it's good enough for me. I
suggest you at least look at it before going down the vmware path - it's
also free software unlike vmware.
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster |
|
| Back to top |
|
 |
tony *nix forums addict
Joined: 08 Mar 2005
Posts: 81
|
Posted: Fri Mar 11, 2005 3:19 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Le vendredi 11 mars 2005 à 16:51 +0100, Magnus Hagander a écrit :
| Quote: | Do *not* do this with a production database.
Vmware does *not* correctly handle fsync()s (or O_SYNC or any of those)
thruogh to disk. If your host PC crashes, your database will almost
certainly be corrupted. fsync() on the client just puts it in the RAM
cache on the host. Not even in the write cache on the disk/raid.
|
Putting Windows NT inside a virtual machine (VMware workstation) solved
all hardware stability problems in my case. NT would only crash if we
forgot to reboot every 45 days or so... The Linux host had a 9 month
uptime at one point.
If you could be more explicit as to why VMware client does not write to
disk I would much appreciate. I was thinking of virtualising a couple of
servers (Linux client on Linux host). TIA
Tony Grant
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org) |
|
| Back to top |
|
 |
Bruce Momjian *nix forums Guru Wannabe
Joined: 02 Mar 2005
Posts: 287
|
Posted: Fri Mar 11, 2005 3:15 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Richard Huxton wrote:
| Quote: | 2. This response is alarming: Tom Lane wrote in digest V1.5092:
We are supporting Windows as a Postgres platform for the benefit of
developers who want to do testing on their laptops (and for reasons
best known to themselves feel a need to run >Windows on their
laptops).
a. Who are the 'we' Tom is talking about?
In an email in the public lists we = Tom
b. Is he speaking for
PostgreSQL Developers and the entire PostgreSQL community?
Official pronouncements from "core" will be marked as such. No-one
speaks for the "entire" PostgreSQL community. You're part of that
community, just by virtue of downloading a copy and subscribing to the
lists.
|
As a core member I can confirm that "we = Tom" in this context. The
core group has made no decisions about the relative stability of Win32
vs Unix, and is unlikely to in the future.
The decision about operating system and stability are to be made by
end-users based on their experience. We do our best to make all
platforms as well supported as possible.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org |
|
| Back to top |
|
 |
tony *nix forums addict
Joined: 08 Mar 2005
Posts: 81
|
Posted: Fri Mar 11, 2005 3:06 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Le vendredi 11 mars 2005 à 10:10 -0500, Richard_D_Levine@raytheon.com a
écrit :
| Quote: | An idea I like, because I have entrenched windows clients also, is to run
things that run best under Linux on VMWare (vmware.com) and to run good
Windows things (like desktop apps) under Windows. Linux can be either the
host or guest OS under VMWare, so the options of which OS is truly in
control are symmetrical. I'm proposing this to my customer to solve a
completely different set of problems (not PostgreSQL related) but the
approach might have merit here as well.
If anyone has tried this please respond.
|
= A man with good ideas! Yes this rocks.
I had a database running like this for quite some time at a clients. It
was an NT server running on a Linux host but other way round it works
just as well. This permits easy replication, easy backup (take a VMware
snapshot of your virtual disk from time to time). I could ssh into the
Linux box and reboot the NT virtual machine after working hours.
Right now the high end virtualisation stuff from the ESX and GSX virtual
machines is trickling down into the Workstation variant. You will be
able to do much more with the VMware 5 Workstation which is on beta test
at the moment.
For all Windows shops this is a very good way of running Linux without
getting your hands dirty. I would recommend
http://lwn.net/Articles/69534/ any distribution based on RHEL. If you
decide to go all the way later you will already have RHEL experience for
$189 outlay - the cost of the VMware workstation licence.
Cheers
Tony
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org |
|
| Back to top |
|
 |
Magnus Hagander *nix forums Guru Wannabe
Joined: 06 Mar 2005
Posts: 158
|
Posted: Fri Mar 11, 2005 2:51 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
| Quote: | An idea I like, because I have entrenched windows clients
also, is to run things that run best under Linux on VMWare
(vmware.com) and to run good Windows things (like desktop
apps) under Windows. Linux can be either the host or guest
OS under VMWare, so the options of which OS is truly in
control are symmetrical. I'm proposing this to my customer
to solve a completely different set of problems (not
PostgreSQL related) but the approach might have merit here as well.
If anyone has tried this please respond.
|
Do *not* do this with a production database.
Vmware does *not* correctly handle fsync()s (or O_SYNC or any of those)
thruogh to disk. If your host PC crashes, your database will almost
certainly be corrupted. fsync() on the client just puts it in the RAM
cache on the host. Not even in the write cache on the disk/raid.
This is vmware workstation, of course. I'm sure their server line of
products act differently.
//Magnus
---------------------------(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 |
|
| Back to top |
|
 |
Guest
|
Posted: Fri Mar 11, 2005 2:10 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
An idea I like, because I have entrenched windows clients also, is to run
things that run best under Linux on VMWare (vmware.com) and to run good
Windows things (like desktop apps) under Windows. Linux can be either the
host or guest OS under VMWare, so the options of which OS is truly in
control are symmetrical. I'm proposing this to my customer to solve a
completely different set of problems (not PostgreSQL related) but the
approach might have merit here as well.
If anyone has tried this please respond.
Thanks,
Rick
Neil Dugan
<postgres@butterflystitc To: pgsql-general@postgresql.org
hes.com.au> cc:
Sent by: Subject: Re: [GENERAL] PostgreSQL still for Linux only?
pgsql-general-owner@post
gresql.org
03/10/2005 05:29 PM
On Thu, 2005-03-10 at 16:19 +0000, Tope Akinniyi wrote:
| Quote: | Hi all,
--- cut ---
I sought Windows replication tool for and could not get. I checked
PgFoundry and the one there put a banner and said NOT FOR WINDOWS.
Then I said is this PostgreSQL for Windows a joke? That prompted
my post - IS POSTGRESQL FOR LINUX ONLY?
|
Have you tried to setup the PostgreSQL server on a Linux computer (with
replication) and use it via PostgreSQL clients running on Windows(tm)
computers. This way your clients will still have the OS they are use to
and the database server will be running on the best OS for it.
--- cut ---
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly |
|
| Back to top |
|
 |
Christopher Browne *nix forums beginner
Joined: 01 Mar 2005
Posts: 14
|
Posted: Fri Mar 11, 2005 1:48 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
That remains to be seen.
I wouldn't consider it the least bit worthwhile to try to evaluate it
now, as what is happening now is that "WinFolk" are getting their very
first exposure to the software.
It would seem surprising for new developers to emerge from the
Windows(tm) population before at least 6 months have passed.
The way developers emerge is that users come along, work with the
software for a while, and discover things that "itch" them the wrong
way. They have become sufficiently committed that it is worth putting
a little effort into scratching some of the itches. That starts
getting them into understanding the code a little better, allowing
them to subsequently scratch deeper itches.
--
output = reverse("moc.liamg" "@" "enworbbc")
http://linuxdatabases.info/info/nonrdbms.html
Share and Enjoy!!
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org) |
|
| Back to top |
|
 |
Christopher Browne *nix forums beginner
Joined: 01 Mar 2005
Posts: 14
|
Posted: Fri Mar 11, 2005 1:40 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Quoth decibel@decibel.org ("Jim C. Nasby"):
| Quote: | With the attitude of "Windows can not be made to reliably run a
database", how many developers do you think will be attracted?
|
That remains to be seen.
I wouldn't consider it the least bit worthwhile to try to evaluate it
now, as what is happening now is that "WinFolk" are getting their very
first exposure to the software.
It would seem surprising for new developers to emerge from the
Windows(tm) population before at least 6 months have passed.
The way developers emerge is that users come along, work with the
software for a while, and discover things that "itch" them the wrong
way. They have become sufficiently committed that it is worth putting
a little effort into scratching some of the itches. That starts
getting them into understanding the code a little better, allowing
them to subsequently scratch deeper itches.
--
output = reverse("moc.liamg" "@" "enworbbc")
http://linuxdatabases.info/info/nonrdbms.html
Share and Enjoy!!
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings |
|
| Back to top |
|
 |
Thomas Hallgren *nix forums beginner
Joined: 10 Mar 2005
Posts: 35
|
Posted: Fri Mar 11, 2005 1:11 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Richard Huxton wrote:
| Quote: | It can also be bad - the more time spent supporting Windows, the less
time is spent working on PostgreSQL itself.
Unless the Windows support attracts more resources. Personally I'd be |
surprised if that's not the case.
| Quote: | That's clearly a decision only you can make. Getting replication working
on Windows will happen quicker the more people help. If all you want is
an off-machine backup, perhaps look at PITR (see manuals for details).
If you're using a Java based client perhaps something like C-JDBC |
http://c-jdbc.objectweb.org would help. It's known to run well with
PostgreSQL.
Regards,
Thomas Hallgren
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly |
|
| Back to top |
|
 |
Dick Davies *nix forums addict
Joined: 11 Mar 2005
Posts: 87
|
Posted: Fri Mar 11, 2005 12:10 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
* Jim C. Nasby <decibel@decibel.org> [0336 21:36]:
| Quote: | With the attitude of "Windows can not be made to reliably run a
database", how many developers do you think will be attracted?
|
People are entitled to an opinion, and in many cases its formed from
experience. I think it's unrealistic to expect a large team of programmers who
have been using *NIX to think windows is equally good.
If they did, they'd run on it, right?
The process model is presumably there because for 90% of platforms it makes
sense to do it that way. No-one is going to object to a well-written thread
based postmaster, but it's expecting a bit much for it to spring into life
off the bat.
To me a database is a service, like a dns or dhcp server, and wanting to
put it on windoms is like wanting to run BIND or IPF on there.
For most people it's going to be easier to stick a linux on a dedicated box
and run postgresql on that. I don't see what the problem is with that.
Just to be clear:
I have no interest or opinion in windows, microsoft or anything else that
makes slashdotters jump up and down beyound playing civ3 on it.
You like it, that's great.
The one thing the world does'nt need is another 'my os can beat up your os'
thread.
--
'That question was less stupid; though you asked it in a profoundly stupid way.'
-- Prof. Farnsworth
Rasputin :: Jack of All Trades - Master of Nuns
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org) |
|
| Back to top |
|
 |
Richard Huxton *nix forums Guru
Joined: 01 Mar 2005
Posts: 522
|
Posted: Fri Mar 11, 2005 7:00 am Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Richard_D_Levine@Raytheon.com wrote:
| Quote: | ...it will be the first time they have seen your name... ...with your first
email have criticised the project...
Check the archives. This poster has been active on the list for awhile.
|
He has indeed, and even posted a news item, but it will still be the
first time many people have seen Tope's name. Given the traffic on the
various lists and the number of new users we've gained recently, you
need to post a *lot* for people to recognise you.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org |
|
| Back to top |
|
 |
Geoffrey *nix forums beginner
Joined: 04 Mar 2005
Posts: 31
|
Posted: Thu Mar 10, 2005 11:09 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
Jim C. Nasby wrote:
| Quote: | On Thu, Mar 10, 2005 at 11:22:59AM -0600, Scott Marlowe wrote:
This is the second problem. Windows simply has problems that cause data
relibility problems that may or may not be surmountable in the future.
Do you have any references to these problems? I've seen several people
mention things like this in passing, but I have yet to see any
specifics.
|
I deal with clients who use all variations of windows OSs. I've
previously worked for a large company who used both Unix and Windows
servers. In every case, the Windows boxes were/are more susceptible to
simply locking up or crashing. When your only resolution is to power
cycle the server, you're going to trash your database. I've seen it on
xp, nt, 200?...
I don't do development on Windows boxes anymore. It's just too
frustrating with the stability issues.
--
Until later, Geoffrey
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org) |
|
| Back to top |
|
 |
Jim Wilson *nix forums beginner
Joined: 10 Mar 2005
Posts: 3
|
Posted: Thu Mar 10, 2005 9:47 pm Post subject:
Re: PostgreSQL still for Linux only?
|
|
|
| Quote: | From: Tope Akinniyi
snip |
experiences. As an IT organisation that wants to stay in business you need to give to people what they wants. I think that is
the basis of service. I have some deployments of PostgreSQL on Windows servers. I must admit that we have not had any problems so
far.
</snip>
Dear Tope,
My apologies that I cannot answer your questions directly, hopefully someone else will on the list.
Understand that this is not really that much of a cultural issue. Both Linux and Postgres are born from interational
cooperation. Even in the United States, windows use is pervasive, with very little support or desire for Linux (or other
non-windows operating systems). The long history of Posix systems in the United States is really limited to educational, research
institutions and a very small percentage of commercial enterprises. Linux has changed this a little over the last 5 years or so.
But I personally know dozens of IT professionals local to my area and only one of them is what I would call a linux expert. This
same ratio applies to the end user market.
If what your customers really want is reliablity and replication options, then that currently conflicts with Windows and
Postgres. Noone can really guarantee that will change. But I submit that if you really want to acheive excellence in the IT
business you will educate yourself and then your customers about using Linux for dedicated database services. You will realize
high reliability and easy maintenance for very low per user cost as compared to just about anything else.
You may want to contact the folks at this web address for local linux support. http://nglug.org/
In any case I wish you the best of luck in your business.
Best regards,
Jim Wilson
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org |
|
| Back to top |
|
 |
Google
|
|
| Back to top |
|
 |
|
|
The time now is Thu Jan 08, 2009 8:04 am | All times are GMT
|
|
Debt Consolidation | Bankruptcy | Power Rangers | Secured Loans | Credit Counseling
|
|
Copyright © 2004-2005 DeniX Solutions SRL
|
|
|
|
Other DeniX Solutions sites:
Unix/Linux blog |
electronics forum |
medicine forum |
science forum |
|
|
Privacy Policy
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|