Writing Commit Status hint bits (was Re: [HACKERS] Constant WAL replay) - Mailing list pgsql-patches

From Simon Riggs
Subject Writing Commit Status hint bits (was Re: [HACKERS] Constant WAL replay)
Date
Msg-id 1121813861.3998.34.camel@localhost.localdomain
Whole thread Raw
Responses Re: Writing Commit Status hint bits (was Re: [HACKERS] Constant WAL replay)
List pgsql-patches
On Sun, 2005-04-24 at 02:28 -0400, Tom Lane wrote:
> In the current code there is no such thing as a hard read-only behavior
> --- for example we will try to update commit-status hint bits no matter
> what.  Allowing that to be turned off would be interesting for a number
> of purposes, such as burning a database onto CD.

Short patch enclosed to turn off writing of commit-status hint bits.

I've called this "cache_txn_status_with_data" but I'm open to other
suggestions...

This should allow migration of older child tables to hierarchical
storage when using a large historical table design.

Best Regards, Simon Riggs

Attachment

pgsql-patches by date:

Previous
From: Mark Wong
Date:
Subject: Re: COPY FROM performance improvements
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [HACKERS] Patch to fix plpython on OS X