Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT) - Mailing list pgsql-patches

From Jeremy Drake
Subject Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)
Date
Msg-id Pine.LNX.4.64.0607021208340.31620@frousa
Whole thread Raw
In response to Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Sun, 2 Jul 2006, Tom Lane wrote:

> Nah, it was a false alarm: I was looking at the first post-patch report,
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mongoose&dt=2006-07-02%2003:30:01
> but apparently mongoose had managed to pick up a partially-updated
> snapshot.  The later reports (including mongoose's own next try an
> hour later) were all OK.

As the keeper of mongoose, is there anything I should do to prevent it
from picking up a partially-updated snapshot?  Or is this just a race
condition that's bound to happen now and then?


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)
Next
From: Bruce Momjian
Date:
Subject: Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)