From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | SODA Noriyuki <soda(at)sra(dot)co(dot)jp> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org, takuya(at)soum(dot)co(dot)jp |
Subject: | Re: "make check" fails over NFS or tmpfs |
Date: | 2006-05-22 14:47:46 |
Message-ID: | 16225.1148309266@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
SODA Noriyuki <soda(at)sra(dot)co(dot)jp> writes:
> On 22 May 2006 03:00:55 -0400, Greg Stark <gsstark(at)mit(dot)edu> said:
> + gcircle_tbl | t
> + gpolygon_tbl | t
>> This seems pretty mystifying. Perhaps it's leftover stuff from the
>> tablespace that failed to get dropped?
> No.
> Because this is a result from tmpfs, and before this failure,
> "make check" passed almost 100 times on this tmpfs.
It looks to me like this is just a possible result from sufficiently
weird timing. gcircle_tbl and gpolygon_tbl are temp tables made in
the create_index test, which runs just before sanity_check. If the
backend running create_index hadn't finished deleting its temp tables
yet, they could still be present when sanity_check looks in pg_class.
Curious that we've never seen this on any other platform though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Armin Massa | 2006-05-22 14:50:33 | Re: Installing PostGreSQL automatically |
Previous Message | Greg | 2006-05-22 14:39:59 | Installing PostGreSQL automatically |