469,898 Members | 1,815 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,898 developers. It's quick & easy.

FW: Postgres alongside MS SQL Server

Hi,

We've got some clients that are concerned about running Postgresql 7.3.4 on
a Win2k Server box, alongside MS SQL Server. I've been running pg on my XP
machines for a long time now (with cygwin) and never had any sort of
problem. The db is fast and stable.

Does anyone have any experience that would give some weight to our client's
concerns? Would there be any potential conflict between the postmaster and
MS SQL Server? Your experience and advice would be greatly appreciated.

-Peter
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 23 '05 #1
6 1878
Hello,

Well it of course depends on what you are doing. Traditionally I would
say, "Are you nuts?" but it really depends
on what you are doing. It is all about risk... if PostgreSQL freaks out
and takes out the machine, what will happen
to the MS SQL server? What about cost associated with downtime?

The same goes for if the MS SQL server takes out the machine? How
important is what PostgreSQL is doing?

Considering you could put together a box that will outperform
PostgreSQL/Cgwin running Linux for about 700 bucks.
Why not just get a new machine and not risk the exposure?

Sincerely,

Joshua D. Drake
Anony Mous wrote:
Hi,

We've got some clients that are concerned about running Postgresql 7.3.4 on
a Win2k Server box, alongside MS SQL Server. I've been running pg on my XP
machines for a long time now (with cygwin) and never had any sort of
problem. The db is fast and stable.

Does anyone have any experience that would give some weight to our client's
concerns? Would there be any potential conflict between the postmaster and
MS SQL Server? Your experience and advice would be greatly appreciated.

-Peter
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 23 '05 #2
Hello,

Well it of course depends on what you are doing. Traditionally I would
say, "Are you nuts?" but it really depends
on what you are doing. It is all about risk... if PostgreSQL freaks out
and takes out the machine, what will happen
to the MS SQL server? What about cost associated with downtime?

The same goes for if the MS SQL server takes out the machine? How
important is what PostgreSQL is doing?

Considering you could put together a box that will outperform
PostgreSQL/Cgwin running Linux for about 700 bucks.
Why not just get a new machine and not risk the exposure?

Sincerely,

Joshua D. Drake
Anony Mous wrote:
Hi,

We've got some clients that are concerned about running Postgresql 7.3.4 on
a Win2k Server box, alongside MS SQL Server. I've been running pg on my XP
machines for a long time now (with cygwin) and never had any sort of
problem. The db is fast and stable.

Does anyone have any experience that would give some weight to our client's
concerns? Would there be any potential conflict between the postmaster and
MS SQL Server? Your experience and advice would be greatly appreciated.

-Peter
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 23 '05 #3
On Thu, Apr 22, 2004 at 09:40:55PM -0600, Anony Mous wrote:
Hi,

We've got some clients that are concerned about running Postgresql 7.3.4 on
a Win2k Server box, alongside MS SQL Server. I've been running pg on my XP
machines for a long time now (with cygwin) and never had any sort of
problem. The db is fast and stable.

Does anyone have any experience that would give some weight to our client's
concerns? Would there be any potential conflict between the postmaster and
MS SQL Server? Your experience and advice would be greatly appreciated.


No, but it's irrelevant. Your clients are idiots who think they know
more about computers than you. You have three choices:

1. Use this as an opportunity to introduce them to low-cost,
highly-functional free Unix systems, i.e. Linux or BSD. They'll thank
you later.

2. Have "the talk" with them. I've done this twice in the last 10
years. Sit them down in a meeting, and simply ask "If you know more
about this than me, then it doesn't make sense that you're paying me
$100/hour to tell you stuff, does it? Do you give your attorney legal
advice, too?" Depends on the client, worked fine for me and in both cases the
clients started treating me very differently after that. I cannot imagine
giving my attorney legal advice, I have no idea why people see this
differently.

3. Convince them that it'll be okay. This is the last piece of advice
because it is the worst. Any time anything goes wrong with the machine
your postgres installation will be the culprit. And stuff will go wrong
daily, if you know what I mean.

It's a difficult situation when you have such clients, but use it as an
opportunity to learn more about doing business.

Michael
--
Michael Darrin Chaney
md******@michaelchaney.com
http://www.michaelchaney.com/

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 23 '05 #4
On Thu, Apr 22, 2004 at 09:40:55PM -0600, Anony Mous wrote:
Hi,

We've got some clients that are concerned about running Postgresql 7.3.4 on
a Win2k Server box, alongside MS SQL Server. I've been running pg on my XP
machines for a long time now (with cygwin) and never had any sort of
problem. The db is fast and stable.

Does anyone have any experience that would give some weight to our client's
concerns? Would there be any potential conflict between the postmaster and
MS SQL Server? Your experience and advice would be greatly appreciated.


No, but it's irrelevant. Your clients are idiots who think they know
more about computers than you. You have three choices:

1. Use this as an opportunity to introduce them to low-cost,
highly-functional free Unix systems, i.e. Linux or BSD. They'll thank
you later.

2. Have "the talk" with them. I've done this twice in the last 10
years. Sit them down in a meeting, and simply ask "If you know more
about this than me, then it doesn't make sense that you're paying me
$100/hour to tell you stuff, does it? Do you give your attorney legal
advice, too?" Depends on the client, worked fine for me and in both cases the
clients started treating me very differently after that. I cannot imagine
giving my attorney legal advice, I have no idea why people see this
differently.

3. Convince them that it'll be okay. This is the last piece of advice
because it is the worst. Any time anything goes wrong with the machine
your postgres installation will be the culprit. And stuff will go wrong
daily, if you know what I mean.

It's a difficult situation when you have such clients, but use it as an
opportunity to learn more about doing business.

Michael
--
Michael Darrin Chaney
md******@michaelchaney.com
http://www.michaelchaney.com/

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 23 '05 #5
At 10:19 AM 4/28/2004 -0600, Anony Mous wrote:
I'm not ruling out the idea of running with a separate linux box, but there
are some strong reasons to stick with the MS box. So, your point is well
taken.

That aside, however, I still need to draw from various people's experience
to get a feel for any problems that may arise when running next to MS SQL
Server. I've heard that Postgresql is a task that runs with "Normal"
priority, and can therefore not lock up the machine to the point where it's
not recoverable. In contrast, I've heard as well that MS SQL Server does
indeed run as a high priority task and will take precedence when the OS
doles out CPU resources.

How is it possible for Postgresql to "freak out" and take out the machine?


How easy/likely is it for a program run as a normal user to blue screen an
MS server?
How easy/likely is it for a program run as a normal user to do the equiv to
a FreeBSD/Linux server?

You can also effectively take out a machine by using too much memory and
going into swap death-spiral.

I'm not sure if it is easy to limit Postgresql memory usage "gracefully" on
an MS box. AFAIK you can do memory limits on Linux/Unix boxes.

MS built-in task manager doesn't let you kill all processes. You need 3rd
party tools to do the equiv of kill -9. But of course you shouldn't kill -9
postgresql. Which brings us to something I don't know the answer of -
what's the safe way of terminating postgresql on a MS server?

Regards,
Link.

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

Nov 23 '05 #6
At 10:19 AM 4/28/2004 -0600, Anony Mous wrote:
I'm not ruling out the idea of running with a separate linux box, but there
are some strong reasons to stick with the MS box. So, your point is well
taken.

That aside, however, I still need to draw from various people's experience
to get a feel for any problems that may arise when running next to MS SQL
Server. I've heard that Postgresql is a task that runs with "Normal"
priority, and can therefore not lock up the machine to the point where it's
not recoverable. In contrast, I've heard as well that MS SQL Server does
indeed run as a high priority task and will take precedence when the OS
doles out CPU resources.

How is it possible for Postgresql to "freak out" and take out the machine?


How easy/likely is it for a program run as a normal user to blue screen an
MS server?
How easy/likely is it for a program run as a normal user to do the equiv to
a FreeBSD/Linux server?

You can also effectively take out a machine by using too much memory and
going into swap death-spiral.

I'm not sure if it is easy to limit Postgresql memory usage "gracefully" on
an MS box. AFAIK you can do memory limits on Linux/Unix boxes.

MS built-in task manager doesn't let you kill all processes. You need 3rd
party tools to do the equiv of kill -9. But of course you shouldn't kill -9
postgresql. Which brings us to something I don't know the answer of -
what's the safe way of terminating postgresql on a MS server?

Regards,
Link.

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

Nov 23 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Adam Kempa | last post: by
2 posts views Thread by Maniek | last post: by
reply views Thread by zerobearing2 | last post: by
reply views Thread by Anony Mous | last post: by
reply views Thread by Peter Lang | last post: by
1 post views Thread by Waqarahmed | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.