Re: Serializable Snapshot Isolation - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Serializable Snapshot Isolation
Date
Msg-id 1284677615-sup-2005@alvh.no-ip.org
Whole thread Raw
In response to Re: Serializable Snapshot Isolation  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Serializable Snapshot Isolation
List pgsql-hackers
Excerpts from Kevin Grittner's message of mié sep 15 14:52:36 -0400 2010:
> Alvaro Herrera <alvherre@commandprompt.com> wrote:
>  
> > I think that would also solve a concern that I had, which is that
> > we were starting to include relcache.h (and perhaps other headers
> > as well, but that's the one that triggered it for me) a bit too
> > liberally, so +1 from me.
>  
> Unfortunately, what I proposed doesn't solve that for relcache.h,
> although it does eliminate lock.h from almost everywhere and htup.h
> from everywhere.

Now that I look at your new patch, I noticed that I was actually
confusing relcache.h with rel.h.  The latter includes a big chunk of our
headers, but relcache.h is pretty thin.  Including relcache.h in another
header is not much of a problem.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: RelationCreateStorage can orphan files
Next
From: "Kevin Grittner"
Date:
Subject: Re: Serializable Snapshot Isolation