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

Re: pgsql: Update item description: * Considerhaving the background writer

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Update item description: * Considerhaving the background writer
Date: 2007-12-21 19:41:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Simon Riggs wrote:
> On Mon, 2007-12-17 at 22:46 +0000, Heikki Linnakangas wrote:
> > I actually do feel it might be valuable. All our opinions are based on 
> > gut-feeling, though, so would need benchmarking to see if it's really 
> > worth it or not.
> > 
> > I think we could get away without accessing system catalogs in bgwriter, 
> > if we flagged heap pages as such in ReadBuffer. Just a thought..
> Well, if you or Bruce or anybody else thinks it should be on the TODO
> then a case should be made for it. I have no doubt you could write it,
> but the point is why would you? Or why would you want somebody else to
> if you're not going to?
> Everybody that spoke on the original thread was against it and I
> specifically mentioned it to kill the idea. Its just plain weird that
> multiple people have given arguments as to why its a bad idea and yet it
> goes straight onto the TODO. LOL.
> If that criteria is used to add stuff to the TODO then it would be
> bursting with crappy ideas...

I saw people saying it could be complex, not that it was a bad idea, and
I just added a description --- the idea was already on the TODO list. 

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-committers by date

Next:From: Bruce MomjianDate: 2007-12-21 21:02:41
Subject: pgsql: Update find_typedefs to handle simple 'typedef X' cases, per
Previous:From: Michael MeskesDate: 2007-12-21 14:33:21
Subject: pgsql: Fixed a few minor glitches pointed out by splint.

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