On 3/14/06, Guido Barosio <[EMAIL PROTECTED]> wrote:
Indeed, from the pg_ctl man pages:``Immediate'' mode will abort all server processes without a cleanshutdown. This will lead to a recovery run on restart.Regards,Guido BarosioOn 3/14/06, Scott Marlowe <
[EMAIL PROTECTED]> wrote:> On Tue, 2006-03-
Indeed, from the pg_ctl man pages:
``Immediate'' mode will abort all server processes without a clean
shutdown. This will lead to a recovery run on restart.
Regards,
Guido Barosio
On 3/14/06, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-03-14 at 14:05, Guido Barosio wrote:
> > Hi Cory
On Tue, 2006-03-14 at 14:05, Guido Barosio wrote:
> Hi Cory,
>
> Actually it seems that the database wasn't shut down properly, and
> while it was doing the recovery, it refused connections. Expected and
> what needs to happen, indeed.
>
> That's why if you are a client about to connect, you'll r
Hi Cory,
Actually it seems that the database wasn't shut down properly, and
while it was doing the recovery, it refused connections. Expected and
what needs to happen, indeed.
That's why if you are a client about to connect, you'll recieve the "
FATAL ...database is starting up " message.
Ideall
Hi all, I'm currently running postgres-7.4.12 with slony-1.0.5 and am seeing the below postgres errors:
Mar 14 00:00:25 master postgres[27357]: [12-1] FATAL: 57P03: the database system is starting up
Mar 14 00:00:25 master postgres[27357]: [12-2] LOCATION: ProcessStartupPacket, postmaster.c:1437
