-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno, would you be willing to write something for docs about how to use
multilog for postgres?
Drew
Bruce Momjian wrote:
| We documented using rotatelogs in the pg_ctl manual page, and have the
| main docs correct on how to use it. Hopefully that will
On Fri, May 21, 2004 at 09:34:04 -0400,
Andrew Hammond <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bruno, would you be willing to write something for docs about how to use
> multilog for postgres?
What are you looking for. Do you need to know about how to in
Jorge Pereira <[EMAIL PROTECTED]> writes:
> I can understand your concerns. But for the sake of context for context,
> here's an example of the code generated by pg_dump --disable-triggers:
I'm well aware of what pg_dump does. Please observe that what it does
(a) affects only one table at a time
Per previous discussions, here are two functions to send INT and TERM
signals to other backends.They permit only INT and TERM, and permits
sending only to postgresql backends (as registered in pgstat).
Documentation to follow. I'd appreciate some pointers as to where to put
this. A new section "Ma
This patch fixes the find_my_exec code for pgstat backends. Required for
TZ stuff (and possibly others) to work in the pgstat backends.
//Magnus
pgstat_exec_cleanup.patch
Description: pgstat_exec_cleanup.patch
---(end of broadcast)---
TIP 8: expla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Wolff III wrote:
| On Fri, May 21, 2004 at 09:34:04 -0400,
| Andrew Hammond <[EMAIL PROTECTED]> wrote:
|
|>-BEGIN PGP SIGNED MESSAGE-
|>Hash: SHA1
|>
|>Bruno, would you be willing to write something for docs about how to use
|>multilog f
On Fri, May 21, 2004 at 16:59:31 -0400,
Andrew Hammond <[EMAIL PROTECTED]> wrote:
>
> I would be insterested in seeing how to set up multilog by it'self. I
> figure that once you get that far, going to daemontools should be pretty
> straighforward. It's also within the scope of Postgres' logging
