From: Tom Lane <tgl@sss.pgh.pa.us>
To: Aaron Werman <awerman2@hotmail.com>
Cc: Iain <iain@mst.co.jp>
Cc: Jim C. Nasby <decibel@decibel.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Tue, 28 Sep 2004 09:58:01 -0400
Message-ID: <14083.1096379881@sss.pgh.pa.us> (raw)
In-Reply-To: <BAY18-DAV126nx8dyDd000801d8@hotmail.com>
References: <b3dc511704092212502a2ddb09@mail.gmail.com>
<20040923152925.18234.qmail@web41114.mail.yahoo.com>
<20040927191836.GS1297@decibel.org>
<00b201c4a4ff$bd73b8b0$7201a8c0@mst1x5r347kymb>
<9617.1096341460@sss.pgh.pa.us>
<BAY18-DAV126nx8dyDd000801d8@hotmail.com>
"Aaron Werman" <awerman2@hotmail.com> writes:
> I imagine a design where a shared plan cache would consist of the plans,
> indexed by a statement hash and again by dependant objects. A statement to
> be planned would be hashed and matched to the cache. DDL would need to
> synchronously destroy all dependant plans. If each plan maintains a validity
^^^^^^^^^^^^^
> flag, changing the cache wouldn't have to block so I don't see where there
^^^^^^^^^^^^^^^^^^^^^^
> would be contention.
You have contention to access a shared data structure *at all* -- for
instance readers must lock out writers. Or didn't you notice the self-
contradictions in what you just said?
Our current scalability problems dictate reducing such contention, not
adding whole new sources of it.
regards, tom lane
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: tgl@sss.pgh.pa.us, awerman2@hotmail.com, iain@mst.co.jp, decibel@decibel.org
Subject: Re: Caching of Queries
In-Reply-To: <14083.1096379881@sss.pgh.pa.us>
* 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