| From: | Jeremy Drake <pgsql-patches(at)jdrake(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-patches(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT) |
| Date: | 2006-07-02 19:12:12 |
| Message-ID: | Pine.LNX.4.64.0607021208340.31620@frousa |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-07-02 19:48:24 | Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT) |
| Previous Message | Andrew Dunstan | 2006-07-02 18:50:18 | Re: [COMMITTERS] pgsql: Do a pass of code review for the |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-07-02 19:48:24 | Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT) |
| Previous Message | Tom Lane | 2006-07-02 16:34:36 | Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT) |