Re: Catalog/Metadata consistency during changeset extraction from wal - Mailing list pgsql-hackers

From David Fetter
Subject Re: Catalog/Metadata consistency during changeset extraction from wal
Date
Msg-id 20120626181154.GB19560@fetter.org
Whole thread Raw
In response to Re: Catalog/Metadata consistency during changeset extraction from wal  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Catalog/Metadata consistency during changeset extraction from wal
List pgsql-hackers
On Mon, Jun 25, 2012 at 01:50:54PM -0500, Kevin Grittner wrote:
> Andres Freund <andres@2ndquadrant.com> wrote:
>  
> > I am not sure were going to get all that into 9.3.
>  
> Sure, that was more related to why I was questioning how much these
> use cases even *could* integrate -- whether it even paid to
> *consider* these use cases at this point.  Responses from Robert and
> you have pretty much convinced me that I was being overly
> pessimistic on that.
>  
> One fine point regarding before and after images -- if a value
> doesn't change in an UPDATE, there's no reason to include it in both
> the BEFORE and AFTER tuple images, as long as we have the null
> column bitmaps -- or some other way of distinguishing unchanged from
> NULL.  (This could be especially important when the unchanged column
> was a 50 MB bytea.)

How about two bitmaps: one telling which columns are actually there,
the other with NULLs?

Cheers,
David.
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: proof concept - access to session variables on client side
Next
From: Merlin Moncure
Date:
Subject: Re: why roll-your-own s_lock? / improving scalability