On Mon, Apr 19, 2004 at 02:58:11PM -0400, Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
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
I've got a problem with these variables in freelist.c:
static int strategy_cdb_found;
static int strategy_cdb_replace;
static int strategy_get_from;
Why are these per-backend? Shouldn't they be in shared state?
regards, tom lane
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
Jan Wieck [EMAIL PROTECTED] writes:
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
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
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
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
Why do we have it at all? Seems like it would be at least as good to
make the T1-or-T2 decision in StrategyGetBuffer, rather than earlier.
If it'd be possible. The problem is that it can get called multiple
times during one logical buffer
