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

Re: A patch for xlog.c

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: A patch for xlog.c
Date: 2001-02-25 20:07:17
Message-ID: Pine.BSF.4.33.0102251606060.32140-100000@mobile.hub.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Sat, 24 Feb 2001, Bruce Momjian wrote:

> > Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org> writes:
> > >> Diffs posted to pgsql-patches are generally considered to be requests
> > >> for application of a patch.  If this is only an experiment it had best
> > >> be clearly labeled as such.
> >
> > > OK.  Is there are better place for discussion of such?
> >
> > pgsql-hackers is the place to discuss anything that's experimental or
> > otherwise concerned with future development.
> >
> > > [ possible merits of mmap ]
> >
> > Let's take up that discussion in pghackers.
>
> I always felt the real benefit of mmap() would be to remove use of SysV
> shared memory and use anon mmap() to prevent problems with SysV share
> memory limits.

You'll still have memory limits to overcome ... per user memory limits
being one ... there is no such thing as a 'cure-all' ...



In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-02-25 20:10:09
Subject: Re: A patch for xlog.c
Previous:From: Kaare RasmussenDate: 2001-02-25 19:06:15
Subject: Monitor status

pgsql-patches by date

Next:From: Bruce MomjianDate: 2001-02-25 20:10:09
Subject: Re: A patch for xlog.c
Previous:From: Tom LaneDate: 2001-02-25 04:28:53
Subject: mmap for zeroing WAL log

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