Re: Separate BLCKSZ for data and logging

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Mark Wong" <markw(at)osdl(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Separate BLCKSZ for data and logging
Date: 2006-03-16 16:30:11
Message-ID: 36e682920603160830i204e82b2o3d61bc26bececb6a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/16/06, Mark Wong <markw(at)osdl(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-03-16 18:12:30 Re: problems compiling CVS HEAD - LDAP auth and Kerberos
Previous Message Mark Wong 2006-03-16 16:21:32 Separate BLCKSZ for data and logging