From: Adrian Klaver <adrian.klaver@aklaver.com> Sent: Sunday, January 27, 2019 8:18:08 PM To: Begin Daniel Cc: pgsql-general Subject: Re: Error message restarting a database
On 1/27/19 2:45 PM, Begin Daniel wrote:
>> If you go to PGDATA.pg_tblspc do you have links to the tablespaces? >> >> I only installed one instance of Postgres on my PC, which I use to manage two databases (postgres and osmdump). osmdump is the database that complains. >> >> Regarding the links to the tablespaces, I first ran the following request. >> SELECT spcname FROM pg_tablespace; and got the following list. >> "pg_default" >> "pg_global" >> "workspace" >> "datadrive1" >> "datadrive2" >> "datadrive3" >> "datadrive0" >> >> I went to E:\pgsqlData\pg_tblspc and found the links to the five last tablespaces above (I manually created them, the first two were created when I installed Postgres). >> E:\pgsqlData\pg_tblspc \113608\PG_9.3_201306121\18364 link to the 888 items mentioned previously (physically stored in K:\pgsqlData\pg_tblspc...) > > Hmm, K:\pgsqlData\pg_tblspc looks suspiciously like something > masquerading as another PGDATA directory. Does a directory listing show > what is shown in?: > > https://www.postgresql.org/docs/10/storage-file-layout.html > >> I also found a PG_VERSION file in E:\pgsqlData. The file contains the value 9.3 >> >> Daniel >> > > Sorry, bad copy paste, you should have read K:\pgsqlData\PG_9.3_201306121\18364 > The suggested content is found only in E:\pgsqlData, including PG_VERSION file and pg_tblspc subdirectory >
Your original post had:
FATAL: ·"pg_tblspc/113608/PG. 9.3_ 201306121/18364" is not a valid data directory
PG. 9.3_ 201306121/18364 does not look like PG_9.3_201306121\18364. To me it looks like a case of corrupted symlink(or whatever it is called on Windows).