Re: Separate BLCKSZ for data and logging - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: Separate BLCKSZ for data and logging
Date
Msg-id 36e682920603160830i204e82b2o3d61bc26bececb6a@mail.gmail.com
Whole thread Raw
In response to Separate BLCKSZ for data and logging  (Mark Wong <markw@osdl.org>)
List pgsql-hackers
On 3/16/06, Mark Wong <markw@osdl.org> wrote:
I've been wondering if there might be anything to gain by having a
separate block size for logging and data.  I thought I might try
defining DATA_BLCKSZ and LOG_BLCKSZ and see what kind of trouble I get
myself into.

If you're going to try it out, here's a starting point based on the block sizes used by Oracle:

512 bytes on Linux, Solaris, AIX, Windows
1K on HP-UX and Tru64
2K on SCO
4K on MVS

--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324

pgsql-hackers by date:

Previous
From: Mark Wong
Date:
Subject: Separate BLCKSZ for data and logging
Next
From: Tom Lane
Date:
Subject: Re: problems compiling CVS HEAD - LDAP auth and Kerberos