I have renamed pgtop.tcl to pgmonitor. I think the new name is clearer.
ftp://candle.pha.pa.us/pub/postgresql/pgmonitor
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I am using the SIGTERM in my administration application to allow
> > administrators to kill individual backends. That is why I noticed the
> > message.
>
> Hm. Of course the backend cannot tell the difference between this use
> of SIGTERM and its
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am using the SIGTERM in my administration application to allow
> administrators to kill individual backends. That is why I noticed the
> message.
Hm. Of course the backend cannot tell the difference between this use
of SIGTERM and its normal use for
Tom Lane wrote:
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> This is a non-improvement. Please reverse it. SIGTERM would only be
> >> sent to a backend if the database system were in fact shutting down.
>
> > But why say the system is shutting down if the backend is shutting down.
> > See
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Also, what signal should people send to a backend to kill just that
> > backend?
>
> I don't know that we do or should recommend such a thing at all ...
> but SIGTERM should work if anything does (and it is, not coincidentally,
> the default kind of
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Also, what signal should people send to a backend to kill just that
> backend?
I don't know that we do or should recommend such a thing at all ...
but SIGTERM should work if anything does (and it is, not coincidentally,
the default kind of signal for ki
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> This is a non-improvement. Please reverse it. SIGTERM would only be
> >> sent to a backend if the database system were in fact shutting down.
>
> > But why say the system is shutting down if the backend is shutting down.
> > Seems the postmaster
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> This is a non-improvement. Please reverse it. SIGTERM would only be
>> sent to a backend if the database system were in fact shutting down.
> But why say the system is shutting down if the backend is shutting down.
> Seems the postmaster should say s
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have applied the following patch to make SIGTERM backend exit clearer
> > in the the server logs. "The system" is not really shutting down, but
> > "the backend" is shutting down.
>
> This is a non-improvement. Please reverse it. SIGTERM would
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have applied the following patch to make SIGTERM backend exit clearer
> > in the the server logs. "The system" is not really shutting down, but
> > "the backend" is shutting down.
>
> This is a non-improvement. Please reverse it. SIGTERM would
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have applied the following patch to make SIGTERM backend exit clearer
> in the the server logs. "The system" is not really shutting down, but
> "the backend" is shutting down.
This is a non-improvement. Please reverse it. SIGTERM would only be
sent
doxygen is a great tool to make code documentation...
It is particulary easy for developpers to add /** **/ comments instead of
/* */ comments that will be extracted by doxygen to make documentation on
functions, structures,...
then you run doxygen from cron and you get automatic API documentat
Rob van Nieuwkerk writes:
> But I still have some worries: is it OK to run pg_dump on *live* databases ?
Yes.
> Do you get consistent dumps from it when there is inserting and updating
> going on ?
Yes.
>"Dumps created by pg_dump are internally consistent, that is, updates
> to the da
Hello,
We have built a database application build around PostgreSQL v7.03.
And we're very happy with PostgreSQL functionality & performance.
In a live situation 50-100 clients are inserting and updating database
records. It is very important that we have all the data available on
the back-up
I have applied the following patch to make SIGTERM backend exit clearer
in the the server logs. "The system" is not really shutting down, but
"the backend" is shutting down.
Should we be showing the PID's in the server logs more. Do we need to
enable that somewhere? Seems they are very hard to
15 matches
Mail list logo
