From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | contrib/lo and restoring databases |
Date: | 2003-03-14 15:12:32 |
Message-ID: | m3ptouf0db.fsf@varsoon.wireboard.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm dumping unrestoreable databases when I use the 'lo' type from
contrib/lo:
lo_test=# select version();
version
-------------------------------------------------------------
PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC 2.96
I'm using contrib/lo because the front-end application is MS Access
(boo hiss) and the ODBC driver requires the 'lo' type in order to use
large objects. However, I can reproduce the problem without involving
Access in any way.
Here's what happens:
issue_track=# \c lo_test;
You are now connected to database lo_test.
lo_test=# create table foo (id serial, object lo);
NOTICE: CREATE TABLE will create implicit sequence 'foo_id_seq' for SERIAL column 'foo.id'
CREATE TABLE
lo_test=# \lo_import /home/netops/tmp/DNS-posture-1.0.pdf
lo_import 20578
lo_test=# insert into foo (object) values (20578::oid::lo);
INSERT 20579 1
lo_test=# select * from foo;
id | object
----+--------
1 | 20578
(1 row)
lo_test=# select distinct loid from pg_largeobject
lo_test-# ;
loid
-------
20578
(1 row)
All well and good so far. I want to make sure I can dump and restore
the database so I do:
bash-2.05a$ pg_dump -Fc -b lo_test >lo_test.dump
bash-2.05a$ createdb -T template0 lo_test2
CREATE DATABASE
bash-2.05a$ pg_restore -v -d lo_test2 < lo_test.dump
pg_restore: connecting to database for restore
pg_restore: creating FUNCTION lo_in (cstring)
pg_restore: NOTICE: ProcedureCreate: type lo is not yet defined
pg_restore: creating FUNCTION lo_out (lo)
pg_restore: NOTICE: Argument type "lo" is only a shell
pg_restore: creating TYPE lo
pg_restore: creating FUNCTION lo_oid (lo)
pg_restore: creating FUNCTION oid (lo)
pg_restore: creating CAST oid (public.lo)
pg_restore: [archiver (db)] could not execute query: ERROR: parser: parse error at or near "." at character 132
pg_restore: *** aborted because of error
This looks like a bug in pg_dump or pg_restore to me. I can supply
the dump file if that would be helpful (it's about 100K).
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-03-14 15:16:40 | Re: constant scalar subselect no longer equivalent to constant? |
Previous Message | James Gregory | 2003-03-14 15:11:47 | nested transactions |