From: Tom Lane <tgl@sss.pgh.pa.us>
To: simon@2ndquadrant.com
Cc: josh@agliodbs.com
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-performance@postgresql.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: Sun, 17 Oct 2004 16:12:35 -0400
Message-ID: <10584.1098043955@sss.pgh.pa.us> (raw)
In-Reply-To: <28292295$10980398474172c227e88c75.95384212@config16.schlund.de>
References: <28292295$10980398474172c227e88c75.95384212@config16.schlund.de>
<simon@2ndquadrant.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, josh@agliodbs.com, pgsql-hackers@postgresql.org
Subject: Re: Re: Getting rid of AtEOXact Buffers (was Re: [Testperf-general] Re: [PERFORM] First set of OSDL Shared Memscalability results, some wierdness ...)
In-Reply-To: <10584.1098043955@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox