Tom Lane-2 wrote:
>
> miller_2555 writes:
>> So this does not work well apparently.
>
> The only obvious thing wrong with your example is failing to preserve
> ownership/permissions of the moved files. I think the upper directories
> are probably not readable by Postgres so it's choking.
>
miller_2555 writes:
> So this does not work well apparently.
The only obvious thing wrong with your example is failing to preserve
ownership/permissions of the moved files. I think the upper directories
are probably not readable by Postgres so it's choking.
BTW, Postgres *already* refers to tab
miller_2555 wrote:
>
> Hi -
> I have a database and used symbolic links in the tablespace
> definitions. I just wanted to validate that I can move the database
> objects to a different physical volume by the following:
> 1) issuing `pg_ctl stop`
> 2) hard copying the tablespace fi
Hi -
I have a database and used symbolic links in the tablespace definitions.
I just wanted to validate that I can move the database objects to a
different physical volume by the following:
1) issuing `pg_ctl stop`
2) hard copying the tablespace files from one drive to another
