From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | pg_dumpall doesn't handle all it should |
Date: | 2000-12-19 19:27:57 |
Message-ID: | 200012191927.eBJJRvc79566@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tomasz Krysinski (tomcio(at)gic(dot)gov(dot)pl) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
pg_dumpall doesn't handle all it should
Long Description
1. it doesn't handle alternate data dirs (just skips the WITH LOCATION statement in CREATE DATABASE). I know it's not the only thing required to recreate such database (a directory must be created and initlocation-ed), but silently skipping the problem doesn't seem to be a good idea.
2. nor does it handle different names for a C shared lib function and an SQL function (skips the C function name in CREATE FUNCTION) which results in failure to recreate when the names differ indeed.
(I suppose pg_dump does the same)
Sample Code
No file was uploaded with this report
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Bunting | 2000-12-19 20:10:48 | ResultSet.getTimestamp() Exception |
Previous Message | pgsql-bugs | 2000-12-19 00:52:05 | CConstraints using inherited attributes fail |