Re: Re: Getting rid of AtEOXact Buffers (was Re: [Testperf-general] Re: [PERFORM] First set of OSDL Shared Memscalability results, some wierdness ...)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: simon(at)2ndquadrant(dot)com
Cc: josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: Re: Re: Getting rid of AtEOXact Buffers (was Re: [Testperf-general] Re: [PERFORM] First set of OSDL Shared Memscalability results, some wierdness ...)
Date: 2004-10-17 20:12:35
Message-ID: 10584.1098043955@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

<simon(at)2ndquadrant(dot)com> writes:
> If the resource owner is always responsible for releasing locked
> buffers, who releases the locks if the backend crashes?

The ensuing system reset takes care of that.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-10-17 21:20:40 Re: Open Items
Previous Message Tom Lane 2004-10-17 19:49:25 Re: strange result from contrib/seg regression on windows

Browse pgsql-performance by date

  From Date Subject
Next Message Gaetano Mendola 2004-10-18 00:22:08 Re: [HACKERS] Getting rid of AtEOXact Buffers (was Re: [Testperf-general]
Previous Message simon 2004-10-17 19:40:01 Re: Getting rid of AtEOXact Buffers (was Re: [Testperf-general] Re: [PERFORM] First set of OSDL Shared Memscalability results, some wierdness ...)