CH <[EMAIL PROTECTED]> writes:
> So the clog is not written to every time the xlog is written to?
No. One clog page holds 32000 transactions' worth of transaction status
values, so on average we need only one clog page write per 32000
transactions.
> On a related issue, what's the connection bet
Hi!
> > Does that mean only the xlog, or also the clog? As far as I understand, the
> > clog contains some meta-information on the xlog, so presumably it is
> > flushed to disc synchronously together with the xlog? That would mean that
> > they each need a separate disk to prevent one disk having
Shridhar Daithankar <[EMAIL PROTECTED]> writes:
> On Wednesday 19 May 2004 13:02, [EMAIL PROTECTED] wrote:
> - If you can put WAL on separate disk(s), all the better.
>>
>> Does that mean only the xlog, or also the clog?
> You can put clog and xlog on same drive.
You can, but I think you shouldn
On Wednesday 19 May 2004 13:02, [EMAIL PROTECTED] wrote:
> > - If you can put WAL on separate disk(s), all the better.
>
> Does that mean only the xlog, or also the clog? As far as I understand, the
> clog contains some meta-information on the xlog, so presumably it is
> flushed to disc synchrono
Hi!
On Mon, May 17, 2004 at 06:04:54PM +0100, Richard Huxton wrote:
> [EMAIL PROTECTED] wrote:
> > [...]
>
> In no official capacity whatsoever, welcome aboard.
Thanks ;-)
> > There is just one point where I found the documentation lacking any
> > description and practical hints (as opposed to
