From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: [PERFORM] First set of OSDL Shared Memscalability results, some wierdness ...)
Date: Sat, 16 Oct 2004 14:18:26 -0700
Message-ID: <200410161418.26557.josh@agliodbs.com> (raw)
In-Reply-To: <4664.1097945657@sss.pgh.pa.us>
References: <NOEFLCFHBPDAFHEIPGBOGEEECGAA.simon@2ndquadrant.com>
<26068.1097872442@sss.pgh.pa.us>
<4664.1097945657@sss.pgh.pa.us>
Tom,
> We could also get rid of the linear search in UnlockBuffers(). The only
> thing it's for anymore is to release a BM_PIN_COUNT_WAITER flag, and
> since a backend could not be doing more than one of those at a time,
> we don't really need an array of flags for that, only a single variable.
> This does not show in the OSDL results, which I presume means that their
> test case is not exercising transaction aborts;
In the test, one out of every 100 new order transactions is aborted (about 1
out of 150 transactions overall).
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: Getting rid of AtEOXact_Buffers (was Re: [Testperf-general] Re: [PERFORM] First set of OSDL Shared Memscalability results, some wierdness ...)
In-Reply-To: <200410161418.26557.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox