[rt-users] Problems upgrading from 3.9.3

saxmad g.mason at fairfx.com
Wed Apr 24 07:06:11 EDT 2013

After a lot of trial and error, I think I have worked out what is going on.

With a clean postgres database, I cannot import my dump file due to the
rtuser role not being there.

So I initialised the database by running the rt-setup-database-4 --action
init utility to put that right.  Unfortunately, part of this seems to be
setting up the initial core data, which looks like it includes the acl

Dropping the database, tables and sequences but leaving the rtuser role
intact, I can then import the dump file without any complaints.  Tables etc
are created and populated, but it does not create the actual rtdb database -
\l within psql does not show an rtdb entry.  I guess that initialising the
database as above would sort that, but then give me the same problem with an
pre-existing acl table.

So I think the answer to my problem is to determine exactly what the pg_dump
command is I need to extract everything from my current RT database in order
for me to be able to import it on my new server without having to initialise
the database first.

The file I am trying to import was created using pg_dump -f ${Dump_File}

I am aware of numerous options to pg_dump, but inexperience means I don't
know which ones to employ in order to get a dump of my RT database with full
integrity to enable a seamless import.

Can someone enlighten me as to exactly how I should use pg_dump to get my
data in a suitable format to enable me to simply import it with psql -f
datafile.sql so I can dop the upgrade cleanly ?

View this message in context: http://requesttracker.8502.n7.nabble.com/Problems-upgrading-from-3-9-3-tp53543p53598.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.

More information about the rt-users mailing list