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

Writing Commit Status hint bits (was Re: [HACKERS] Constant WALreplay)

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Writing Commit Status hint bits (was Re: [HACKERS] Constant WALreplay)
Date: 2005-07-19 22:57:41
Message-ID: 1121813861.3998.34.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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: hintbits.patch
Description: text/x-patch (2.5 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2005-07-19 23:06:00
Subject: Re: [HACKERS] Patch to fix plpython on OS X
Previous:From: Palle GirgensohnDate: 2005-07-19 22:54:34
Subject: Re: More buildfarm stuff

pgsql-patches by date

Next:From: Jim C. NasbyDate: 2005-07-19 23:06:00
Subject: Re: [HACKERS] Patch to fix plpython on OS X
Previous:From: Mark WongDate: 2005-07-19 22:51:33
Subject: Re: COPY FROM performance improvements

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