> 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

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

On Mon, Apr 04, 2005 at 02:50:30PM -0400, Merlin Moncure wrote:

> > 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.

Hmm. I'll keep that in consideration (if we come to implement lock
table spilling.)

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

Not right now.

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
Este mail se entrega garantizadamente 100% libre de sarcasmo.

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org