"Alexander A. Blashko" wrote:
>
> [EMAIL PROTECTED] wrote:
> >I'd like to define a few terms here - my word usages
> >may not match
> >other people's:
> >
> >1. Logging - capturing and recording data about events happening
> >in the system.
> >
> >2. Journalling - capturing database transactions
[EMAIL PROTECTED] wrote:
>I'd like to define a few terms here - my word usages
>may not match
>other people's:
>
>1. Logging - capturing and recording data about events happening
>in the system.
>
>2. Journalling - capturing database transactions
>
>3. Mirroring - exactly replicating database acti
[EMAIL PROTECTED] wrote:
>
> > > I need a logging utility for postgresql server.
> > This will (probably) be addressed in WAL (write-ahead logging(?)), due to
> > appear eventually but, as we found out the other day, not so soon :( .
> Can i write any log anywhere? My first goal was to duplicat
> > I need a logging utility for postgresql server.
> This will (probably) be addressed in WAL (write-ahead logging(?)), due to
> appear eventually but, as we found out the other day, not so soon :( .
Can i write any log anywhere? My first goal was to duplicate the
database, for more safety. Ther
On 1999-12-11, [EMAIL PROTECTED] mentioned:
> I need a logging utility for postgresql server.
This will (probably) be addressed in WAL (write-ahead logging(?)), due to
appear eventually but, as we found out the other day, not so soon :( .
--
Peter Eisentraut Sernanders väg 10:
Hi all!
I need a logging utility for postgresql server.
The log server (and the file) shall be on not the same machine like
postgresql server, so the last good database impresson will be exists if the
master issue destroyd.
Thats needed a logging facility in postgres server, who send all off writ
