Обсуждение: Postgresql 9.5 error

Поиск
Список
Период
Сортировка

Postgresql 9.5 error

От
Yogi Barot
Дата:

Hi,

 

I have migrated data from postgresql 9.0 to 9.5, When I run following command, it does not show tablespace location and fails with bellow error. Can someone provide fix in the next release?


We are planning to put release in production from March 15, hopefully get fix before this date.

 

postgres=# select * from pg_tablespace;  -- Spclocation column is missing in pg_tablespace.

     spcname     | spcowner | spcacl | spcoptions

-----------------+----------+--------+------------

pg_default      |       10 |        |

pg_global       |       10 |        |

foa_table_space |    16384 |        |

(3 rows)

 

postgres=# \db*

ERROR:  column "spclocation" does not exist

LINE 3:   spclocation AS "Location"

 

Thanks,

Yogi

 

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.

Re: Postgresql 9.5 error

От
Thomas Kellerer
Дата:
Yogi Barot schrieb am 18.02.2016 um 15:14:
> I have migrated data from postgresql 9.0 to 9.5, When I run following command, it does not
> show tablespace location and fails with bellow error. Can someone provide fix in the next release?
>
>
> We are planning to put release in production from March 15, hopefully get fix before this date.
>
> postgres=# select * from pg_tablespace;  -- Spclocation column is missing in pg_tablespace.
>
>      spcname     | spcowner | spcacl | spcoptions
>
> -----------------+----------+--------+------------
> pg_default      |       10 |        |
> pg_global       |       10 |        |
> foa_table_space |    16384 |        |
>
> (3 rows)
>
> *postgres=# \db**
> *ERROR:  column "spclocation" does not exist*
> *LINE 3:   spclocation AS "Location"*


From the 9.2 release notes:

E.16.2. Migration to Version 9.2

    Remove the spclocation field from pg_tablespace (Magnus Hagander)

    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.

Re: Postgresql 9.5 error

От
Tom Lane
Дата:
Yogi Barot <YBarot@symcor.com> writes:
> I have migrated data from postgresql 9.0 to 9.5, When I run following command, it does not show tablespace location
andfails with bellow error. Can someone provide fix in the next release? 

> postgres=# \db*
> ERROR:  column "spclocation" does not exist
> LINE 3:   spclocation AS "Location"

You're apparently trying to use an old version of psql with the newer
database.  You need to use an up-to-date psql.

            regards, tom lane

Re: Postgresql 9.5 error

От
Steve Crawford
Дата:
You are probably using an old client with a new server. Update the client first.

Cheers,
Steve


On Thu, Feb 18, 2016 at 6:14 AM, Yogi Barot <YBarot@symcor.com> wrote:

Hi,

 

I have migrated data from postgresql 9.0 to 9.5, When I run following command, it does not show tablespace location and fails with bellow error. Can someone provide fix in the next release?


We are planning to put release in production from March 15, hopefully get fix before this date.

 

postgres=# select * from pg_tablespace;  -- Spclocation column is missing in pg_tablespace.

     spcname     | spcowner | spcacl | spcoptions

-----------------+----------+--------+------------

pg_default      |       10 |        |

pg_global       |       10 |        |

foa_table_space |    16384 |        |

(3 rows)

 

postgres=# \db*

ERROR:  column "spclocation" does not exist

LINE 3:   spclocation AS "Location"

 

Thanks,

Yogi

 


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.

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin


Re: Postgresql 9.5 error

От
Steve Crawford
Дата:
To expand on my earlier response, I can force this exact error if I use psql 9.1 to connect to a 9.5 server. During upgrades it is recommended to always update your clients, not only psql but any software that uses the client libs, first and then upgrade the server.

Cheers,
Steve

On Thu, Feb 18, 2016 at 6:14 AM, Yogi Barot <YBarot@symcor.com> wrote:

Hi,

 

I have migrated data from postgresql 9.0 to 9.5, When I run following command, it does not show tablespace location and fails with bellow error. Can someone provide fix in the next release?


We are planning to put release in production from March 15, hopefully get fix before this date.

 

postgres=# select * from pg_tablespace;  -- Spclocation column is missing in pg_tablespace.

     spcname     | spcowner | spcacl | spcoptions

-----------------+----------+--------+------------

pg_default      |       10 |        |

pg_global       |       10 |        |

foa_table_space |    16384 |        |

(3 rows)

 

postgres=# \db*

ERROR:  column "spclocation" does not exist

LINE 3:   spclocation AS "Location"

 

Thanks,

Yogi

 


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.

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin


Re: Postgresql 9.5 error

От
Yogi Barot
Дата:

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: Steve Crawford [mailto:scrawford@pinpointresearch.com]
Sent: Thursday, February 18, 2016 10:03 AM
To: Yogi Barot
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgresql 9.5 error

 

To expand on my earlier response, I can force this exact error if I use psql 9.1 to connect to a 9.5 server. During upgrades it is recommended to always update your clients, not only psql but any software that uses the client libs, first and then upgrade the server.

 

Cheers,

Steve

 

On Thu, Feb 18, 2016 at 6:14 AM, Yogi Barot <YBarot@symcor.com> wrote:

Hi,

 

I have migrated data from postgresql 9.0 to 9.5, When I run following command, it does not show tablespace location and fails with bellow error. Can someone provide fix in the next release?


We are planning to put release in production from March 15, hopefully get fix before this date.

 

postgres=# select * from pg_tablespace;  -- Spclocation column is missing in pg_tablespace.

     spcname     | spcowner | spcacl | spcoptions

-----------------+----------+--------+------------

pg_default      |       10 |        |

pg_global       |       10 |        |

foa_table_space |    16384 |        |

(3 rows)

 

postgres=# \db*

ERROR:  column "spclocation" does not exist

LINE 3:   spclocation AS "Location"

 

Thanks,

Yogi

 

 

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.



--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

 

Re: Postgresql 9.5 error

От
Igor Neyman
Дата:

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

Re: Postgresql 9.5 error

От
Yogi Barot
Дата:

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.