Re: unlogged tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: unlogged tables
Date: 2010-11-16 20:08:24
Message-ID: AANLkTikRazDB6fFPNoH1fqD7NZCegNwvN65WPgtEW_FY@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 16, 2010 at 2:49 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On lör, 2010-11-13 at 19:16 -0500, Robert Haas wrote:
>> 1. The first one (relpersistence-v1) is a mostly mechanical patch that
>> replaces pg_class.relistemp (a Boolean) with pg_class.relpersistence
>> (a character), so that we can support more than two values.  BE SURE
>> YOU INITDB, since the old catalog format will not work with this patch
>> applied.
>
> Btw., I would recommend that even in-progress or proposed patches
> include catversion updates, which helps communicate the message such as
> yours in a more robust manner and also reduces the chance of forgetting
> the catversion change in the final commit.

I thought we had a policy of NOT doing that, because of the merge
conflicts thereby created. It's also hard to know what value to set
it to; whatever you pick will certainly be obsolete by commit time.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-11-16 20:26:17 Re: unlogged tables
Previous Message Jignesh Shah 2010-11-16 20:08:16 Re: possible concurrency bug or mistake in understanding read-committed behavior