# You won't get any support for performance issue if you changed the default
# schema.
#
-bindir=@SQL_BINDIR@
+bindir=@POSTGRESQL_BINDIR@
PATH="$bindir:$PATH"
db_name=${db_name:-@db_name@}
-- In general, these will cause very significant performance
-- problems in other areas. A better approch is to carefully check
-- that all your memory configuation parameters are
--- suitable for the size of your installation. If you backup
+-- suitable for the size of your installation. If you backup
-- millions of files, you need to adapt the database memory
-- configuration parameters concerning sorting, joining and global
-- memory. By default, sort and join parameters are very small
JobId integer not null,
PathId integer not null,
FilenameId integer not null,
+ DeltaSeq smallint not null default 0,
MarkId integer not null default 0,
LStat text not null,
Md5 text not null,
CREATE TABLE RestoreObject (
RestoreObjectId SERIAL NOT NULL,
ObjectName TEXT NOT NULL,
- RestoreObject TEXT NOT NULL,
+ RestoreObject BYTEA NOT NULL,
PluginName TEXT NOT NULL,
ObjectLength INTEGER DEFAULT 0,
+ ObjectFullLength INTEGER DEFAULT 0,
ObjectIndex INTEGER DEFAULT 0,
ObjectType INTEGER DEFAULT 0,
- FileIndex INTEGER UNSIGNED DEFAULT 0,
- JobId INTEGER UNSIGNED,
+ FileIndex INTEGER DEFAULT 0,
+ JobId INTEGER,
ObjectCompression INTEGER DEFAULT 0,
- PRIMARY KEY(RestoreObjectId),
+ PRIMARY KEY(RestoreObjectId)
);
CREATE INDEX restore_jobid_idx on RestoreObject(JobId);
INSERT INTO Status (JobStatus,JobStatusLong,Severity) VALUES
('i', 'Doing batch insert file records',15);
-INSERT INTO Version (VersionId) VALUES (12);
+INSERT INTO Version (VersionId) VALUES (@BDB_VERSION@);
-- Make sure we have appropriate permissions