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

Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Make the visibility map crash-safe.
Date: 2011-06-30 22:19:09
Message-ID: 1309472349.31501.1.camel@jdavis-ux.asterdata.local (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Thu, 2011-06-30 at 07:50 -0400, Robert Haas wrote:
> I compare the performance of commit
> 431ab0e82819b31fcd1e33ecb52c2cd3b4b41da7 (post-patch) with commit
> 431ab0e82819b31fcd1e33ecb52c2cd3b4b41da7 (pre-patch).

I believe that is a copy/paste error.

Regards,
	Jeff Davis


In response to

Responses

pgsql-hackers by date

Next:From: Thom BrownDate: 2011-06-30 22:28:17
Subject: Re: reducing the overhead of frequent table locks, v4
Previous:From: Merlin MoncureDate: 2011-06-30 20:42:26
Subject: Re: hint bit cache v6

pgsql-committers by date

Next:From: Bruce MomjianDate: 2011-07-01 22:17:41
Subject: pgsql: Change pg_upgrade to use port 50432 by default to avoidunintend
Previous:From: Devrim GÜNDÜZDate: 2011-06-30 20:00:03
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID

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