From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jakub Ouhrabka <kuba@comgate.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: Linux/PostgreSQL scalability issue - problem with 8 cores
Date: Fri, 11 Jan 2008 10:05:40 -0500
Message-ID: <12997.1200063940@sss.pgh.pa.us> (raw)
In-Reply-To: <47874EE8.2050406@comgate.cz>
References: <flii57$748$1@news.hub.org>
<7083.1199379570@sss.pgh.pa.us>
<477D1D59.7050002@comgate.cz>
<4782063C.7070105@comgate.cz>
<26502.1199745090@sss.pgh.pa.us>
<4782AB4D.8010009@comgate.cz>
<27655.1199750492@sss.pgh.pa.us>
<47836A4C.5080707@comgate.cz>
<10713.1199813111@sss.pgh.pa.us>
<47874EE8.2050406@comgate.cz>
Jakub Ouhrabka <kuba@comgate.cz> writes:
> We'we tried hard to identify what's the cause of filling sinval-queue.
> We went through query logs as well as function bodies stored in the
> database. We were not able to find any DDL, temp table creations etc.
Strange. The best idea that comes to mind is to add some debugging
code to SendSharedInvalidMessage to log the content of each message
that's sent out. That would at least tell us *what* is going into
the queue, even if not directly *why*. Try something like (untested)
void
SendSharedInvalidMessage(SharedInvalidationMessage *msg)
{
bool insertOK;
+ elog(LOG, "sending inval msg %d %u %u %u %u %u",
+ msg->cc.id,
+ msg->cc.tuplePtr.ip_blkid.bi_hi,
+ msg->cc.tuplePtr.ip_blkid.bi_lo,
+ msg->cc.tuplePtr.ip_posid,
+ msg->cc.dbId,
+ msg->cc.hashValue);
+
LWLockAcquire(SInvalLock, LW_EXCLUSIVE);
insertOK = SIInsertDataEntry(shmInvalBuffer, msg);
LWLockRelease(SInvalLock);
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, kuba@comgate.cz
Subject: Re: Linux/PostgreSQL scalability issue - problem with 8 cores
In-Reply-To: <12997.1200063940@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