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

Re: Notes on lock table spilling

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl>,"Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Notes on lock table spilling
Date: 2005-04-04 18:50:30
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3415C235C@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-hackers
> On Wed, 2005-03-30 at 18:09 -0400, Alvaro Herrera wrote:
> > I'm seeing what can I do about spilling the lock table to disk
> > I welcome comments on the ideas outlined here.  If anyone sees a
> > showstopper please let me know.
> 
> Perhaps a little delayed, but yes, I have major reservations about the
> whole concept of spilling the lock table to disk. If you implement
this,
> I would very much like a switch to be able to turn it off, somehow.

me too.  I very much like the current behavior, so that a transaction is
aborted when lock table space is exhausted.  This is pretty flexible
because you can always manipulate the lock table size.  However,
Alvaro's stuff would still be nice when doing massive database changes
that are not performance sensitive.

By the way Alvaro, are you still planning to reorganize the lock union?

Merlin

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2005-04-04 19:02:47
Subject: Re: Notes on lock table spilling
Previous:From: Simon RiggsDate: 2005-04-04 18:08:11
Subject: Re: Notes on lock table spilling

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