BUG #5080: test tablespace failure

Started by Seneca Cunninghamover 16 years ago2 messagesbugs
Jump to latest
#1Seneca Cunningham
tentra@gmail.com

The following bug has been logged online:

Bug reference: 5080
Logged by: Seneca Cunningham
Email address: tentra@gmail.com
PostgreSQL version: 8.4.1
Operating system: OS X 10.6.0
Description: test tablespace failure
Details:

thucydides:postgresql-8.4.1 seneca$ ./configure --prefix=/opt/pgsql841
[...]
thucydides:postgresql-8.4.1 seneca$ make -j5
[...]
All of PostgreSQL successfully made. Ready to install.
thucydides:postgresql-8.4.1 seneca$ make check
[...]
test stats ... ok
test tablespace ... FAILED
============== shutting down postmaster ==============
server stopped

========================
1 of 120 tests failed.
========================

The differences that caused some tests to fail can be viewed in the
file "/opt/src/postgresql-8.4.1/src/test/regress/regression.diffs". A copy
of the test summary that you see
above is saved in the file
"/opt/src/postgresql-8.4.1/src/test/regress/regression.out".

make[2]: *** [check] Error 1
make[1]: *** [check] Error 2
make: *** [check] Error 2
thucydides:postgresql-8.4.1 seneca$

*** /opt/src/postgresql-8.4.1/src/test/regress/expected/tablespace.out 
2009-09-24 19:38:21.000000000 -0400
--- /opt/src/postgresql-8.4.1/src/test/regress/results/tablespace.out  
2009-09-24 19:39:08.000000000 -0400
***************
*** 72,74 ****
--- 72,75 ----
  drop cascades to table testschema.atable
  -- Should succeed
  DROP TABLESPACE testspace;
+ ERROR:  could not read directory "pg_tblspc/40203": Invalid argument

======================================================================

/opt/src/postgresql-8.4.1/src/test/regress/regression.diffs (END)

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Seneca Cunningham (#1)
Re: BUG #5080: test tablespace failure

"Seneca Cunningham" <tentra@gmail.com> writes:

-- Should succeed
DROP TABLESPACE testspace;
+ ERROR:  could not read directory "pg_tblspc/40203": Invalid argument

This is a known bug in Snow Leopard :-(. We are expecting that Apple
will fix it soon, though they failed to do so in 10.6.1.

regards, tom lane