From: | Tory M Blue <tmblue(at)gmail(dot)com> |
---|---|
To: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | pg_upgrade custom table locations. Move table locations during upgrade? |
Date: | 2020-02-27 20:40:20 |
Message-ID: | CAEaSS0Y5+eSGTk0CFsqO7Zb7G+dK4efRTYEV4cokBLVKqk1fxw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Many decades ago (small fib).
There was a write up of someone stopping the postgres upgrade at a certain
point, editing a file with the table locations and then restarting the
upgrade process.
"Now, what are you trying to do?"
I have version specific directories (good for you), but...
/pgsql/9.5/tablespaces
I am updating to 12 and thus
/pgsql/12/tablespaces (is where I would like them).
Using the -link, it simples creates the PG12, files under
/pgsql/9.5/tablespace
I'd like to , even when using link, to say don't do that, but instead
please link the Ver 12 tables to /pgsql/12/tablespaces.
The information is in the file
pg_upgrade_dump_globals.sql:CREATE TABLESPACE "torquespace" OWNER "cls"
LOCATION '/pgsql/9.5/torque';
but while it's there, I'd like it not to be there (and it's possible that
I'm running into an initial design flaw and the table spaces should really
be under /pgsql and not /pgsql/$VERSION/
However is there a way to say create the new links under /pgsql/12/ vs
/pgsql/9.5/ using the pg_upgrade process?
Thanks
Tory
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Brannen | 2020-02-27 20:42:36 | RE: trouble making PG use my Perl |
Previous Message | Tom Lane | 2020-02-27 20:14:05 | Re: Is it safe to rename an index through pg_class update? |