[Bizgres-general] [Fwd: Writing Commit Status hint bits ( was Re: [HACKERS] Constant WAL replay)]

[Luke Lonergan]

Simon - is this one an enabler for constant WAL replay?  Can you give a
short benefits / risk analysis?

Thanks!

- Luke 


On 7/19/05 3:59 PM, "Simon Riggs" <simon at 2ndquadrant.com> wrote:

> Just submitted to pgsql-patches at postgresql.org ...
> 
> 
> -------- Forwarded Message --------
> From: Simon Riggs <simon at 2ndquadrant.com>
> To: pgsql-patches at postgresql.org
> Cc: Tom Lane <tgl at sss.pgh.pa.us>
> Subject: Writing Commit Status hint bits (was Re: [HACKERS] Constant WAL
> replay)
> Date: Tue, 19 Jul 2005 23:57:41 +0100
> 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
> _______________________________________________
> Bizgres-general mailing list
> Bizgres-general at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/bizgres-general