"Chad R. Larson" <clarson@eldocomp.com> writes:
> At 08:25 AM 8/13/02 , Robert M. Meyer wrote:
>> I had the same problem. I rewrote my shutdown script to call 'pg_ctl -m
>> immediate'. So far, I haven't seen any damage because of it and we always
>> restart tomcat at some point in the middle of the night, anyway.
> We're running PostgreSQL as a backend to a J2SE server (with Macromedia
> JRun instead of Tomcat). When we converted our Sun Enterprise servers into
> a cluster (Veritas VCS) we had similar problems. We were using the "fast"
> option on a shutdown, but switchover in the cluster would hang until we
> changed the "fast" to "immediate". We'd prefer "fast", but it does not
> seem to work exactly as documented.
> Solaris 2.6, PostgreSQL 7.1.2, VCS 1.1.
FYI, I think the cause of this has finally been identified -- a client
that sits idle for long enough to let the SI buffer overrun means that
its connected backend will ignore "fast" shutdown requests for as long
as the client continues to do nothing. The bug exists in 7.1 through
current. I just posted a patch to pgsql-admin.
regards, tom lane
