Hi, Martin,
Martin Pitt wrote:
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
Hi, Martin,
Martin Pitt schrieb:
In the earlier postgresql instalations, one could define environment
variables in postgresql.env or postmaster.conf which then were exported
to the postmaster, and we could use it as LOCATION when creating new
databases in other locations.
These files are
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
tag 340166 moreinfo
thanks
Hi Markus!
Markus Schaber [2005-11-21 14:40 +0100]:
In the earlier postgresql instalations, one could define environment
variables in postgresql.env or postmaster.conf which then were exported
to the postmaster, and we could use it as LOCATION when creating new
Package: postgresql-7.4
Version: 1:7.4.8-17
Severity: normal
Hi,
Some time ago, I crossgraded the Postgresql 7.4 installation to the
new postgresql-common and postgresql-7.4 packaging.
In the earlier postgresql instalations, one could define environment
variables in postgresql.env or
5 matches
Mail list logo
