Stuart Bishop wrote:
-- Start of PGP signed section.
Arnaud Lesauvage wrote:
Hi list !
I have a small enterprise network (~15 workstations, 1 server), all
running windows OSes. Most of our work is done on a PostgreSQL DB (on
the windows server).
I am the only IT here, and my boss
Bruce Momjian wrote:
Stuart Bishop wrote:
-- Start of PGP signed section.
Arnaud Lesauvage wrote:
Hi list !
I have a small enterprise network (~15 workstations, 1 server), all
running windows OSes. Most of our work is done on a PostgreSQL DB (on
the windows server).
I am the only IT here, and
Joshua D. Drake wrote:
Bruce Momjian wrote:
Stuart Bishop wrote:
-- Start of PGP signed section.
Arnaud Lesauvage wrote:
Hi list !
I have a small enterprise network (~15 workstations, 1 server), all
running windows OSes. Most of our work is done on a PostgreSQL DB (on
the windows
I guess the users would start over anyway. So easiest if you
provide a copy of the app with that other connection and
signal them if the first server dies to just close the first
and start the backup-application.
This requires that all the users do the right thing. Problem is, what if
there
Scott Ribe a écrit :
I prefer the approach of keeping the backup server up to date, whether using
PITR or Slony or your own home-grown synching, and then changing IPs. My
process involves someone making the decision that server is indeed down,
then UNPLUGGING it from the network, then changing
But you have a point that having a contact for postgresql support is a
very good idea anyway !
Here ya go:
http://www.commandprompt.com/support
(DISCLAIMER: I represent the company)
Josh, don't you think the better starting point when looking for support
would be
Michael Meskes a écrit :
Josh, don't you think the better starting point when looking for support
would be http://www.postgresql.org/support/professional_support ? :-)
There are support companies in France and other parts of Europe which
might be a better idea for a company in France. After all
Hi list !
I have a small enterprise network (~15 workstations, 1 server),
all running windows OSes. Most of our work is done on a PostgreSQL
DB (on the windows server).
I am the only IT here, and my boss asked me to find a way to have
the database always online, without my intervention.
Last
Hi Arnaud,
perhaps you can still use Slony-I for replication and have another tool
automatically handle connections (check out PgPool[1] or SQLRelay[2]).
Or go for a middleware replication solution. Check C-JDBC[3], perhaps
there is something similar for ODBC?
LifeKeeper seems to handle
Markus Schiltknecht a écrit :
Hi Arnaud,
perhaps you can still use Slony-I for replication and have another tool
automatically handle connections (check out PgPool[1] or SQLRelay[2]).
Or go for a middleware replication solution. Check C-JDBC[3], perhaps
there is something similar for ODBC?
Hi list !
I have a small enterprise network (~15 workstations, 1
server), all running windows OSes. Most of our work is done
on a PostgreSQL DB (on the windows server).
I am the only IT here, and my boss asked me to find a way to
have the database always online, without my intervention.
Magnus Hagander a écrit :
Since you're a Windows shop, you may already have the experience (and
even liceneses perhaps?) to run Microsoft Cluster Service (part of 2003
Enterprise Edition or 2000 Advanced Server). PostgreSQL will work fine
with it. Works with shared disks using either
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Arnaud Lesauvage
Sent: 31 May 2006 10:39
To: Magnus Hagander
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Best high availability solution ?
Otherwise, is the clustering service
Dave Page a écrit :
Slony-I only exists for Windows in a not-even-beta state at the moment,
so even if you get things up and running using a virtual IP solution you
will be hand-holding Slony until it gets properly released.
OK, I thought it was in production stage.
If I'm honest, I think
Arnaud Lesauvage schrieb:
...
I think you're right.
Is there a simple replication solution for windows then ? Or will I have
to stop the master postgresql at night to pgdump and pgrestore on the
backup server ?
pg_dump does not require you to stop the master database anyway.
(in fact it
-Original Message-
From: Arnaud Lesauvage [mailto:[EMAIL PROTECTED]
Sent: 31 May 2006 11:27
To: Dave Page
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Best high availability solution ?
Dave Page a écrit :
Slony-I only exists for Windows in a not-even-beta state
Arnaud Lesauvage schrieb:
Tino Wildenhain a écrit :
pg_dump does not require you to stop the master database anyway.
(in fact it cannot even dump a stopped database :-)
Hello Tino,
I think I might just use this pg_dump solution...
Seems to be quite simple to set up.
personally I think
Dave Page a écrit :
The code is written, and is good as far as we are aware, but has not been
through a beta/release cycle yet.
OK, that's already pretty good then.
Are there binary releases available ?
Is there a simple replication solution for windows then ? Or will
I have to stop the
-Original Message-
From: Arnaud Lesauvage [mailto:[EMAIL PROTECTED]
Sent: 31 May 2006 11:53
To: Dave Page
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Best high availability solution ?
Dave Page a écrit :
The code is written, and is good as far as we are aware
Tino Wildenhain a écrit :
personally I think the WAL approach is by far easier
to set up and maintain - the pg_dump is in fact easy,
but the restore to another database can be tricky
if you want it unattended and bullit-proof the same
time.
I'll have to study this more in-depth then.
If I got
Dave Page a écrit :
http://developer.pgadmin.org/~hiroshi/Slony-I/
That's built against 8.1 iirc.
Great !
USE AT YOUR OWN RISK!! IT MAY EAT YOUR DATA AND SET YOUR SERVER ON FIRE :-)
I'll keep an eye on it then ! ;-)
--
Arnaud
---(end of
Arnaud Lesauvage schrieb:
Tino Wildenhain a écrit :
personally I think the WAL approach is by far easier
to set up and maintain - the pg_dump is in fact easy,
but the restore to another database can be tricky
if you want it unattended and bullit-proof the same
time.
I'll have to study this
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tino
Wildenhain
Sent: 31 May 2006 12:14
To: Arnaud Lesauvage
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Best high availability solution ?
Then with a script that would change my
Dave Page a écrit :
Yes - the DNS method would work, but you might run into caching issues
requiring the users to reboot or do a 'ipconfig /flushdns' before they
see the change.
Yes, but I am not a very nice adminsitrator, and when there is any
problem with a datawase, my users HAVE to reboot
-Original Message-
From: Arnaud Lesauvage [mailto:[EMAIL PROTECTED]
Sent: 31 May 2006 12:33
To: Dave Page
Cc: Tino Wildenhain; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Best high availability solution ?
Dave Page a écrit :
Yes - the DNS method would work, but you
Dave Page a écrit :
Ah, but wasn't this intended for when you are not there standing over them with
a bat?
:-)
It was, but they know I will come back from vacation one day, and
then
;-)
--
Arnaud
---(end of broadcast)---
TIP 1: if
In the last exciting episode, dpage@vale-housing.co.uk (Dave Page) wrote:
If I'm honest, I think your boss is going to be disappointed. You
would add a *lot* of complexity to the system to make it handle
failures with zero intervention, and that extra complexity is
probably more likely to go
Stuart Bishop a écrit :
If your application is normally reliable, I think the best, cheapest and
simplest way of keeping the system online when you are on leave is to give
your work the phone number of a company offering PostgreSQL support
services. I would avoid adding the extra complexity and
Since you're a Windows shop, you may already have the
experience (and
even liceneses perhaps?) to run Microsoft Cluster Service
(part of 2003
Enterprise Edition or 2000 Advanced Server). PostgreSQL will
work fine
with it. Works with shared disks using either fibrechannel or iSCSI.
Arnaud Lesauvage wrote:
Hi list !
I have a small enterprise network (~15 workstations, 1 server), all
running windows OSes. Most of our work is done on a PostgreSQL DB (on
the windows server).
I am the only IT here, and my boss asked me to find a way to have the
database always online,
At 10:38 AM 5/31/2006 +0200, Magnus Hagander wrote:
Since you're a Windows shop, you may already have the experience (and
even liceneses perhaps?) to run Microsoft Cluster Service (part of 2003
Enterprise Edition or 2000 Advanced Server). PostgreSQL will work fine
with it. Works with shared
On Wed, May 31, 2006 at 09:36:23 +0200,
Arnaud Lesauvage [EMAIL PROTECTED] wrote:
I am the only IT here, and my boss asked me to find a way to have
the database always online, without my intervention.
Last time I went on vacation, the server crashed and no one was
able to repair it.
Your
Bruno Wolff III a écrit :
On Wed, May 31, 2006 at 09:36:23 +0200,
Arnaud Lesauvage [EMAIL PROTECTED] wrote:
I am the only IT here, and my boss asked me to find a way to have
the database always online, without my intervention.
Last time I went on vacation, the server crashed and no one was
I agree with you, but I will have two servers : one will be the file
server, the primary controller of the active directory, and the backup
of postgresql; the other one will be the postgresql server and the
backup of the file server and active directory.
So restoring from this situation does
34 matches
Mail list logo
