RE: Problem starting up Postgres from pulse

From: Edward Croft [mailto:[email protected]] 
Sent: Wednesday, June 18, 2003 5:49 PM
To: [email protected]
Subject: Problem starting up Postgres from pulse

Hi all, inching ever closer to being able to deploy AS, however a number
of issues have come up. I need to resolve these before plunking down
$1500 for the full version. 

1.) If both servers start up at approximately the same time, both
attempt to start the database. This is not good since they share the
same directory for data. Is there a way to prevent this from happening?
I know that this would be a rare instance, but they want no loopholes. 

The solution in this case is to disable automatic start on power-up of the
database. It has to be done always manually. The reason for this is that
sometimes you have to perform integrity checks on the database prior to
putting it in service. What you must provide is a documented procedure to
power up & down the system.

2.) Updates? I had to patch the kernel in order for FOS to be able to
run scripts. Will this patch be included in future versions? Is the RH
Enterprise Linux AS the same version as the Developer Edition? Or will I
have to restart all my patching/testing/et al from scratch?

The only way to get a precise answer short of diverse speculations is to
contact the sales service of RedHat and try to get the information. Normally
they should be the same but it highly likely that some functionality may be
implemented in different ways in the developer and production versions.

3.) I had used up2date to attempt to update a freshly installed copy of
RHAS Dev and it said that it was up to date. What about all the kernel
patches? Security releases, notably the sendmail and bind issues. 

The fresh copy if it installed online is higly likely to be updated. Check
the software versions of the installed packeges with those provided in the
erratas. If they are the same you have no need of updates. Otherwise up2date
has some disabled functionality.

The end of your problems is to contact RedHat and buy the product using a
written contract that clears out all the problems related to compatibility
and upgrade procedures.

I am trying to move ahead with this, but these issues have come up and
caused alarms with my QA department. 

Any help would be appreciated,
Ed Croft, RHCE


_______________________________________________
Piranha-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/piranha-list