On Mon, 20 Dec 2010, Adrian Klaver wrote:
Well that would be a problem. Still, using pg_ctl would be an improvement.
From the docs
(http://www.postgresql.org/docs/9.0/interactive/app-pg-ctl.html): "pg_ctl
is a utility for initializing a PostgreSQL database cluster, starting,
stopping, or restart
On Monday 20 December 2010 7:12:52 pm Rich Shepard wrote:
> On Mon, 20 Dec 2010, Adrian Klaver wrote:
> > As I remember it there was more than one version of Postgres on this
> > machine. Are you sure you are using the correct postgres binary? While I
> > am it is there a reason you are not using t
On Mon, 20 Dec 2010, John R Pierce wrote:
if you built and installed postgres in /usr/local/pgsql, then all those
errors should have referred to /usr/local/pgsql/share/timezone
John,
I assumed the reference to share/ was relative to /usr/local/pgsql/
is there a different postgres binary i
On Mon, 20 Dec 2010, Adrian Klaver wrote:
As I remember it there was more than one version of Postgres on this
machine. Are you sure you are using the correct postgres binary? While I
am it is there a reason you are not using the system start scripts or
pg_ctl:)?
Adrian,
There _was_ a libra
On 12/20/10 5:09 PM, Rich Shepard wrote:
I built and installed -9.0.1 on my Slackware-13.1 server and it ran
for a
while. Now, without warning, one of my applications dependent upon
postgres
won't run. While trying to restart postgres I learned the .pid file
did not
exist so I removed /tmp/.
On Monday 20 December 2010 5:09:24 pm Rich Shepard wrote:
>I built and installed -9.0.1 on my Slackware-13.1 server and it ran for
> a while. Now, without warning, one of my applications dependent upon
> postgres won't run. While trying to restart postgres I learned the .pid
> file did not exis
