Skip site navigation (1) Skip section navigation (2)

Re: SSI patch version 14

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Dan Ports" <drkp(at)csail(dot)mit(dot)edu>
Cc: <simon(at)2ndQuadrant(dot)com>,<markus(at)bluegap(dot)ch>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSI patch version 14
Date: 2011-02-09 15:58:50
Message-ID: 4D52655A020000250003A6D7@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Dan Ports <drkp(at)csail(dot)mit(dot)edu> wrote:
 
> I think for SerializableXidHash we should probably just initially
> allocate it at its maximum size. Then it'll match the PredXact
> list which is allocated in full upfront, and there's no risk of
> being able to allocate a transaction but not register its xid. In
> fact, I believe there would be no way for starting a new
> serializable transaction to fail.
 
To be more precise, it would prevent an out of shared memory error
during an attempt to register an xid for an active serializable
transaction.  That seems like a good thing.  Patch to remove the
hint and initially allocate that HTAB at full size attached.
 
I didn't attempt to address the larger general issue of one HTAB
stealing shared memory from space calculated to belong to another,
and then holding on to it until the postmaster is shut down.
 
-Kevin

Attachment: ssi-full-xid-alloc.patch
Description: text/plain (1.8 KB)

In response to

Responses

pgsql-hackers by date

Next:From: David FetterDate: 2011-02-09 16:00:58
Subject: Re: [COMMITTERS] pgsql: Remove more SGML tabs.
Previous:From: Markus WannerDate: 2011-02-09 15:38:35
Subject: Re: SSI patch version 14

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group