I found the culprit env variable was defined as PG_DATA inlieu of PGDATA
cleared and dropped itand restarted dband created once again tablespace in the
desired location and it worked
Thank YouRegards
On Friday, December 20, 2024 at 11:50:20 AM EST, Adrian Klaver
<adrian.kla...@aklaver.com> wrote:
On 12/20/24 08:09, Bharani SV-forum wrote:
> Adrian
> Inline image
>
> initially i had created tblspace outside pg_data env variable
Did you run CREATE TABLESPACE as shown below?:
https://www.postgresql.org/docs/current/sql-createtablespace.html
Did you ever use the tablespace?
> e.g PG_DATA env variable is defined to /XXX/YYYY/ABC/15/data
>
> the tablespace was created under /XXX/YYYY/ABC/15/tblspace/<<tbl_spcname>>/
> assume tablespace name is abc_data
>
> *cd /XXX/YYYY/ABC/15/tblspace/abc_data/*
> ls -atl
> drwxr-x---. 2 postgres postgres 6 Dec 19 22:08 PG_15_202209061
>
> ls -altR
> drwxr-x---. 2 postgres postgres 6 Dec 19 22:08 PG_15_202209061
>
> i reconfirmed
> SELECT * FROM pg_tablespace ;
> oid | spcname | spcowner | spcacl | spcoptions
> ------+------------+----------+--------+------------
> 1663 | pg_default | 10 | |
> 1664 | pg_global | 10 | |
>
> not having any entry about tablespace abc_data
>
> Can you guide
>
--
Adrian Klaver
adrian.kla...@aklaver.com
