pg.ddx.io  pgsql-students@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Florian G. Pflug <fgp@phlo.org>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-students@postgresql.org
Subject: Re: Final status of projects?
Date: Thu, 30 Aug 2007 00:13:58 +0200
Message-ID: <46D5EFA6.4020406@phlo.org> (raw)
In-Reply-To: <1188422745.4199.14.camel@ebony.site>
References: <200708291042.31584.josh@agliodbs.com>
	<46D5B238.1040006@phlo.org>
	<1188422745.4199.14.camel@ebony.site>

Simon Riggs wrote:
> On Wed, 2007-08-29 at 19:51 +0200, Florian G. Pflug wrote:
>> Josh Berkus wrote:
>>> Students & Mentors,
>>>
>>> I'd like to know how all of your projects came out.  I know about a few of 
>>> them, but not a lot of the others:
>>>
>>> Florian -- still working on HOT Standby
>> PITR standby you mean, I think ;-)
> 
> Hmmm, well if we say Hot Standby rather than HOT Standby. We need to
> differentiate what we have now ("warm") with what we hope to achieve
> ("hot"). (I do have to say I've been amazed at how many people seem to
> have confused what Florian is working on).
When I read HOT, I immediatly thought "Heap-Only-Tuples", because I've
been reading that patch, to see if we can reuse some ideas for
lazy xid assignment. So I didn't even consider that HOT could mean hot ;-)

>> I have completed an early prototype. Since the pencils-down dealine of
>> GSoC has already passed (It was 20th August), I'm currently working on
>> a patch to lazily assign XIDs. This is a generalization of a part of
>> my GSoC work, since readonly queries on PITR standby instances need to
>> be able to run without a real XID too (We cannot generate XIDs on the
>> standby, they might conflict with those generated on the master).
>>
>> If this patch should go in, it'll remove one obstacle from the way
>> to readonly-queries on PITR slaves, and make the rest of the patch
>> a great deal less intrusive.
> 
> I'm very happy with what has been achieved, but we really should regard
> this as research and not committable code. In this case, the idea of
> "pencils down" doesn't make any sense.
Full Ack. The fact that what I do now won't be part of the "official SoC 
outcome" anyway just made it easier for me to justify my little "lazy
XID assignment" detour.

greetings, Florian Pflug




view thread (15+ messages)  latest in thread

Message-ID: <46D5EFA6.4020406@phlo.org>
Permalink:  ../46D5EFA6.4020406@phlo.org/
Also on:    postgresql.org/message-id/46D5EFA6.4020406@phlo.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-students@postgresql.org
  Cc: fgp@phlo.org, simon@2ndquadrant.com, josh@agliodbs.com
  Subject: Re: Final status of projects?
  In-Reply-To: <46D5EFA6.4020406@phlo.org>
  References: <200708291042.31584.josh@agliodbs.com> <46D5B238.1040006@phlo.org> <1188422745.4199.14.camel@ebony.site> <46D5EFA6.4020406@phlo.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox