Re: Why are these ARC variables per-backend?

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Why are these ARC variables per-backend?
Date: 2004-04-19 17:39:14
Message-ID: 40840EC2.4060209@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> I've got a problem with these variables in freelist.c:
>
> static int strategy_cdb_found;
> static int strategy_cdb_replace;

These two most definitely are per backend because they hold status
information about the blocks this backend specifically is mucking with.
If it all would be in one function, they would be local variables.

> static int strategy_get_from;

This one is questionable. The point of it is to steer the T1/T2 list
sizes towards the goal of the strategy (T1_target). It doesn't matter
much if this is off by one every now and then, it will be corrected at
the next buffer eviction ... or the one after that.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Hallgren 2004-04-19 17:43:57 Re: GUC variable set, TODO
Previous Message Bruce Momjian 2004-04-19 17:26:52 CSV patch applied