Re: [PATCH] Relocation of tablespaces in pg_basebackup
От | Gabriele Bartolini |
---|---|
Тема | Re: [PATCH] Relocation of tablespaces in pg_basebackup |
Дата | |
Msg-id | 52CF14D1.2060403@2ndQuadrant.it обсуждение исходный текст |
Ответ на | Re: [PATCH] Relocation of tablespaces in pg_basebackup (Steeve Lennmark <steevel@handeldsbanken.se>) |
Ответы |
Re: [PATCH] Relocation of tablespaces in pg_basebackup
|
Список | pgsql-hackers |
Hi Steeve, > Il 09/01/14 22:10, Steeve Lennmark ha scritto: > > That's a much better solution, I attached a patch with the updated code. > > # SELECT oid, pg_tablespace_location(oid) FROM pg_tablespace; > [...] > 16388 | /tmp/tblspc1 > 16389 | /tmp/tblspc2 I'd suggest, a similar solution to the one we have adopted in Barman (if you don't know it: www.pgbarman.org), that is: --tablespace NAME:LOCATION [--tablespace NAME:location] I prefer this over the location on the master as this might change over time (at least more frequently than the tablespace name) and over servers. > $ pg_basebackup -Xs -D backup/data -T /tmp/tblspc1:$(pwd)/backup/t1 -T > /tmp/tblspc2:$(pwd)/backup/t2 With the above example, it would become: $ pg_basebackup -Xs -D backup/data -T tblspc1:$(pwd)/backup/t1 -T tblspc2:$(pwd)/backup/t2 Thanks, Gabriele -- Gabriele Bartolini - 2ndQuadrant ItaliaPostgreSQL Training, Services and Supportgabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
В списке pgsql-hackers по дате отправления: