Hi Markus! Markus Schaber [2006-01-01 12:03 +0100]: > http://www.postgresql.org/docs/7.4/interactive/manage-ag-alternate-locs.html > documents this behaviour.
Ah, I see. Thank you. > >>Not only that the environment variable setting was not migrated, I also > >>did not find the right place to reinstantiate this setting. > > > > I see, so you defined PGDATAEXTERN in postgresql.env? What does this > > variable do? It is not documented anywhere and not present in the > > default postgresql.env or postmaster.conf files. > > Yes, I defined it in postgresql.env, and then used it in "createdb > --location=PGDATAEXTERN" when creating the database. > > I used to have this setting in the init.d scripts, but as an apt-get > upgrade overwrote this file, I was told to use postmaster.env instead. I > don't remember whether there was an official bug filing, or this was > private email. I did never see that bug, so maybe it was in a private email to Oliver Elphick? > As a workaround until all 7.4 databases are migrated, I just want to > know the right place where to hack in this environment variable, so the > postmaster process can access it. As far as I can see, an equivalent to the old postgresql.env file seems to make sense and would also offer a transition path for the old /etc/postgresql/postgresql.env file. So if postgresql-common would support /etc/postgresql/version/cluster/environment, then you could add these variables there, and the transitional postgresql package could move postgresql.env there. Do you agree? Thanks, Martin -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org In a world without walls and fences, who needs Windows and Gates?
signature.asc
Description: Digital signature
