Subject: Re: initdb errors, postgresql-8.0-beta - msg#00348

Previous Message by Date: click to view message preview

Re: Apologies if you don't consider this a bug and I've wasted your time.

Steve Ingram <ingram@xxxxxxxxxxxxx> writes: > When I pg_dump out the database, it outputs all the tables, functions, types > as you'd expect, but it outputs table definitions that reference postgis > functions/types *before* the functions/types themselves. Yeah, this is pretty likely if you did any ALTER TABLE or similar commands anywhere along the line. The dump order is dependent on the original creation order of the objects (tables, functions, etc) and so it's pretty easy to break it by adding columns or indexes to pre-existing tables. 8.0's pg_dump attempts to deal with this by paying attention to dependencies, but no earlier release does anything at all credible. FWIW, pg_restore does have options to alter the reload order, which may be an easier workaround than editing a textual dump. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings

Next Message by Date: click to view message preview

BUG #1236: still in use tablespaces can be removed

The following bug has been logged online: Bug reference: 1236 Logged by: Fabien Email address: coelho@xxxxxxxxxxxx PostgreSQL version: 8.0 Beta Operating system: Linux debian Description: still in use tablespaces can be removed Details: Sorry if this bug was already reported. I could not search the list as http://archives.postgresql.org/pgsql-bugs/ looks blank right now... One can remove a tablespace although it is being used, putting the database in a slightly incoherent state. It was so in yesterday (27/08/2004) cvs head: sh> mkdir /tmp/postgres pg> CREATE TABLESPACE tsp LOCATION '/tmp/postgres'; -- ok pg> CREATE SCHEMA s TABLESPACE tsp; -- ok pg> DROP TABLESPACE tsp; -- ok... pg> CREATE TABLE s.t(id SERIAL PRIMARY KEY); -- ERROR... cannot create directory The bug is simply that DROP TABLESPACE looks whether the directory is empty, but it happens that the namespace's tablespace uses do not create anything in the directory... I now that I can alter the tablespace entry manually in pg_namespace to correct this, but it looks like a bug to me anyway: the database should not be so easy to put in a in coherent state. Suggested fix: create some empty file in the directory if it is used by a namespace. don't forget to move the file around when altering the namespace (well, once it will be implemented). It does not seems practical to check for namespace's uses of a tablespace as one belong to a cluster and the other to the database. ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@xxxxxxxxxxxxxx

Previous Message by Thread: click to view message preview

initdb errors, postgresql-8.0-beta

============================================================================ POSTGRESQL BUG REPORT TEMPLATE ============================================================================ Your name : Murthy Your email address : smk_va@xxxxxxxxx System Configuration --------------------- Architecture (example: Intel Pentium) : Intel PIII DP Operating System (example: Linux 2.4.18) : Fedora Core 2, linux 2.6.8.1 smp PostgreSQL version (example: PostgreSQL-8.0): PostgreSQL-8.0 (beta), source downloaded from ftp3.us.postgresql.org Compiler used (example: gcc 2.95.2) : gcc 3.3.3 Please enter a FULL description of your problem: ------------------------------------------------ I was able to successfully compile postogresql-8.0-beta (make check reporteed "Passed all 96 tests"). However, it appears that postresql was compiled with the wrong value of --pkglibdir: rather than libdir = $PREFIX/lib it was compiled with libdir = $PREFIX/bin/lib, but make install put "lib/" in $PREFIX/lib. This might have been as issue with the "share/" dir as well as I have to give the -L option to initdb and ln -s ../lib lib in $PREFIX bin, before initdb returned success. HTH, Murthy Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: ---------------------------------------------------------------------- If you know how this problem might be fixed, list the solution below: --------------------------------------------------------------------- __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend

Next Message by Thread: click to view message preview

Postgres 8.0.0b1 build on Solaris 10 Ultrasparc

hello all, here follows the regression test run on postgres 8.0.0b1. Hardware Ultra 2 dual 300MHz CPUS 768MB RAM OS Solaris 10 b 5 ------------------------------ ============== creating temporary installation ============== ============== initializing database system ============== ============== starting postmaster ============== running on port 65432 with pid 15380 ============== creating database "regression" ============== CREATE DATABASE ALTER DATABASE ============== dropping regression test user accounts ============== ============== installing PL/pgSQL ============== ============== running regression test queries ============== parallel group (13 tests): boolean char text varchar name int4 int8 oid int2 float4 bit float8 numeric boolean ... ok char ... ok name ... ok varchar ... ok text ... ok int2 ... ok int4 ... ok int8 ... ok oid ... ok float4 ... ok float8 ... ok bit ... ok numeric ... ok test strings ... ok test numerology ... ok parallel group (20 tests): point lseg path box circle polygon timetz time date interval abstime tinterval timestamp comments reltime inet timestamptz type_sanity oidjoins opr_sanity point ... ok lseg ... ok box ... ok path ... ok polygon ... ok circle ... ok date ... ok time ... ok timetz ... ok timestamp ... ok timestamptz ... ok interval ... ok abstime ... ok reltime ... ok tinterval ... ok inet ... ok comments ... ok oidjoins ... ok type_sanity ... ok opr_sanity ... ok test geometry ... ok test horology ... ok test insert ... ok test create_function_1 ... ok test create_type ... ok test create_table ... ok test create_function_2 ... ok test copy ... ok parallel group (7 tests): create_aggregate create_operator triggers vacuum constraints inherit create_misc constraints ... ok triggers ... ok create_misc ... ok create_aggregate ... ok create_operator ... ok inherit ... ok vacuum ... ok parallel group (2 tests): create_view create_index create_index ... ok create_view ... ok test sanity_check ... ok test errors ... ok test select ... ok parallel group (18 tests): select_into select_having select_distinct_on select_distinct case union aggregates random update select_implicit transactions namespace hash_index join arrays btree_index portals subselect select_into ... ok select_distinct ... ok select_distinct_on ... ok select_implicit ... ok select_having ... ok subselect ... ok union ... ok case ... ok join ... ok aggregates ... ok transactions ... ok random ... ok portals ... ok arrays ... ok btree_index ... ok hash_index ... ok update ... ok namespace ... ok test privileges ... ok test misc ... ok parallel group (5 tests): portals_p2 select_views cluster rules foreign_key select_views ... ok portals_p2 ... ok rules ... ok foreign_key ... ok cluster ... ok parallel group (14 tests): limit temp sequence truncate polymorphism copy2 prepare conversion rangefuncs domain rowtypes without_oid plpgsql alter_table limit ... ok plpgsql ... ok copy2 ... ok temp ... ok domain ... ok rangefuncs ... ok prepare ... ok without_oid ... ok conversion ... ok truncate ... ok alter_table ... ok sequence ... ok polymorphism ... ok rowtypes ... ok test stats ... ok test tablespace ... ok ============== shutting down postmaster ============== postmaster stopped ====================== All 96 tests passed. ====================== rm regress.o make[2]: Leaving directory `/export/DATA/BUILD/postgresql-8.0.0beta1/src/test/regress' make[1]: Leaving directory `/export/DATA/BUILD/postgresql-8.0.0beta1/src/test' ------------------------------- No more errors as in Solaris 9. regards, Andre Martano ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend