On Thu, 2019-11-21 at 09:11 -0600, Ron wrote:
> After adding another 350GB to the data/base filesystem, the storage team
> said that the virtual LUN on our ESX host is full. No more expansion of
> this database until and unless they create a new LUN (on storage replicated
> to a different DC using SRM).
>
> Thus, to enlarge the database on this VM, we either...
>
> 1. create a tablespace on a different (modest sized) LUN, or
> 2. create a completely new 10TB LUN and migrate the whole db (including
> backups) to that new LUN.
>
> Honestly, using a new tablespace seems simpler.
Ok, that is a valid use case :^)
Change into the directory with the new file system.
Create a subdirectory and "chown" it to "postgres".
Become operating system user "postgres" and verify
that you can write to that directory.
If not, fix the permissions of the directories on the path.
If you can write to the directory, you will be able to create
a tablespace there.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com