On 14th of July, Alvaro Herrera committed patch:
psql: Show tablespace size in \db+ Fabrízio de Royes Mello
Continue reading Waiting for 9.5 – psql: Show tablespace size in \db+
On 14th of July, Alvaro Herrera committed patch:
psql: Show tablespace size in \db+ Fabrízio de Royes Mello
Continue reading Waiting for 9.5 – psql: Show tablespace size in \db+
On 18th of January, Stephen Frost committed patch:
Add ALTER TABLESPACE ... MOVE command This adds a 'MOVE' sub-command to ALTER TABLESPACE which allows moving sets of objects from one tablespace to another. This can be extremely handy and avoids a lot of error-prone scripting. ALTER TABLESPACE ... MOVE will only move objects the user owns, will notify the user if no objects were found, and can be used to move ALL objects or specific types of objects (TABLES, INDEXES, or MATERIALIZED VIEWS).
He followed it, with another commit:
Add CREATE TABLESPACE ... WITH ... Options Tablespaces have a few options which can be set on them to give PG hints as to how the tablespace behaves (perhaps it's faster for sequential scans, or better able to handle random access, etc). These options were only available through the ALTER TABLESPACE command. This adds the ability to set these options at CREATE TABLESPACE time, removing the need to do both a CREATE TABLESPACE and ALTER TABLESPACE to get the correct options set on the tablespace. Vik Fearing, reviewed by Michael Paquier.
Really cool news. Thanks to sponsoring from AWeber.com, and code by Brian Dunavant OmniPITR has now support for additional tablespaces in backup creation.
This works on both master and slave, and happens automatically without any kind of user interaction or changing options – OmniPITR simply detects if you have additional tablespaces and backs them up to data tarball.
More details are places in TABLESPACES part of omnipitr-backup-* docs.