Skip site navigation (1) Skip section navigation (2)

Re[3]: Re: [PATCHES] A patch for xlog.c

From: jamexu <jamexu(at)telekbird(dot)com(dot)cn>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re[3]: Re: [PATCHES] A patch for xlog.c
Date: 2001-02-27 03:18:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Hello The,

Tuesday, February 27, 2001, 11:00:05 AM, you wrote:

THH> On Tue, 27 Feb 2001, jamexu wrote:

>> Hello Tom,
>> Tuesday, February 27, 2001, 12:23:25 AM, you wrote:
>> TL> This looks a lot like exchanging the devil we know (SysV shmem) for a
>> TL> devil we don't know.  Do I need to remind you about, for example, the
>> TL> mmap bugs in early Linux releases?  (I still vividly remember having to
>> TL> abandon mmap on a project a few years back that needed to be portable
>> TL> to Linux.  Perhaps that colors my opinions here.)  I don't think the
>> TL> problems with shmem are sufficiently large to justify venturing into
>> TL> a whole new terra incognita of portability issues and kernel bugs.
>> TL>                         regards, tom lane
>> the only problem is because if we need to tune Postermaster to use
>> large buffer while system havn't so many SYSV shared memory, in many
>> systemes, we need to recompile OS kernel, this is a small problem to install
>> PGSQL to product environment.

THH> What?  You don't automatically recompile your OS kernel when you build a
THH> system in the first place??  First step on any OS install of FreeBSD is to
THH> rid myself of the 'extras' that are in the generic kernel, and enable
THH> SharedMemory (even if I'm not using PgSQL on that machine) ...

heihei, why do you think users always using FreeBSD and not other
UNIX systemes?
your assume is false.

Xu Yifeng

In response to


pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2001-02-27 03:41:12
Subject: vacuum analyze fails: ERROR: Unable to locate type oid 2230924 in catalog
Previous:From: Tom LaneDate: 2001-02-27 03:16:35
Subject: Re: COPY doesn't works when containing ' ' or ' ' characters on db

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group