Re: Postgresql 9.5 error - Mailing list pgsql-admin
From | Yogi Barot |
---|---|
Subject | Re: Postgresql 9.5 error |
Date | |
Msg-id | 353d125c324241b09f8a7e003df93f72@MX002.symprod.com Whole thread Raw |
In response to | Re: Postgresql 9.5 error (Igor Neyman <ineyman@perceptron.com>) |
List | pgsql-admin |
Great. It worked. Thanks a lot.
From: Igor Neyman [mailto:ineyman@perceptron.com]
Sent: Thursday, February 18, 2016 10:25 AM
To: Yogi Barot; 'Steve Crawford'
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Postgresql 9.5 error
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Yogi Barot
Sent: Thursday, February 18, 2016 10:05 AM
To: 'Steve Crawford' <scrawford@pinpointresearch.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgresql 9.5 error
Ok Got it, I found bellow:
spclocation is deprecated.
This field was duplicative of the symbolic links that actually define tablespace locations, and thus risked errors of omission when moving a tablespace. This change allows tablespace directories to be moved while the server is down, by manually adjusting the symbolic links. To replace this field,
we have added pg_tablespace_location() to allow querying of the symbolic links
But, how to update tablespace location in 9.5? I moved tablespace to different location, what is next step now?
Thanks,
From http://www.postgresql.org/docs/9.5/static/manage-ag-tablespaces.html :
The directory $PGDATA/pg_tblspc contains symbolic links that point to each of the non-built-in tablespaces defined in the cluster. Although not recommended, it is possible to adjust the tablespace layout by hand by redefining these links. Under no circumstances perform this operation while the server is running. Note that in PostgreSQL 9.1 and earlier you will also need to update the pg_tablespace catalog with the new locations.
Regards,
Igor Neyman
CONFIDENTIALITY WARNING
This communication, including any attachments, is for the exclusive use of addressee and may contain proprietary and/or confidential information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
AVERTISSEMENT RELATIF À LA CONFIDENTIALITÉ
Ce message, ainsi que les pièces qui y sont jointes, est destiné à l’usage exclusif de la personne à laquelle il s’adresse et peut contenir de l’information personnelle ou confidentielle. Si le lecteur de ce message n’en est pas le destinataire, nous l’avisons par la présente que toute diffusion, distribution, reproduction ou utilisation de son contenu est strictement interdite. Veuillez avertir sur-le-champ l’expéditeur par retour de courrier électronique et supprimez ce message ainsi que toutes les pièces jointes.
pgsql-admin by date: