base/1 instead of base/template1 initdb result
base/1 instead of base/template1 initdb result
От:
Jean-Roch SCHMITT <jean-roch.schmitt@cybercable.fr>
Дата:
I can't find any reports on this problem : On MacOS X (darwin), the initdb command creates, as the template, the "base/1" directory intead of "base/template1". Further databases creation is then possible but this odd directory naming prevents correct pg_upgrade operations from Postgres databases created on Solaris, for instance. Any hints ? TIA
Re: base/1 instead of base/template1 initdb result
От:
Peter Eisentraut <peter_e@gmx.net>
Дата:
Jean-Roch SCHMITT writes: > I can't find any reports on this problem : > On MacOS X (darwin), the initdb command creates, as the template, the > "base/1" directory > intead of "base/template1". Further databases creation is then possible > but this odd directory > naming prevents correct pg_upgrade operations from Postgres databases > created on Solaris, for instance. Firstly, this is the correct new naming scheme in PostgreSQL (on any platform). Secondly, it wouldn't be possible to use pg_upgrade between different architectures anyway. Thirdly, it wouldn't be possible to use pg_upgrade to move from 7.0 to 7.1 anyway. Fourthly, pg_upgrade no longer exists. -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/