Shawn, You must be logged in as the "root" or "postgres" user. Otherwise the "ps aux"
can't work proper way.
The fact, that the files postmaster are in the directory/folder doesn't mean that it
is properly instaled.
shaman dan peder
-Original Message-
From: Shawn Pursley [SMTP:[EMAI
Simon --
Thanks for all the help so far...please don't kill me...
For anyone else doing this exercise...I had to use the -R instead of -r on
Mandrake.
[root@pusher bin]# chown -R postgres /usr/local/pgsql/
[postgres@pusher pgsql]$ nohup postmaster > regress.log 2>&1 &
[1] 1443
[postgres@pusher
On Tue, 24 Aug 1999, Shawn Pursley wrote:
> Simon --
>
> Thanks for all the help so far...please don't kill me...
>
> For anyone else doing this exercise...I had to use the -R instead of -r on
> Mandrake.
Yeah, my bad - it is indeed -R
>
> [root@pusher bin]# chown -R postgres /usr/local/pg
The Hermit Hacker wrote:
>
> Morning ...
>
> After spending the past while looking at the pitiful creation I
> created, we've finally taken the time to redo the site so that, in our
> opinion, it looks professional...
>
> "Take a look at us now" - http://www.pgsql.com
>
>
Hmm...tried to submit a suggestion via the contact page,
but it reports back
Not Found
The requested URL /contact.cgi was not found on this server.
Cheers, Thomas
> Subject: Re: [GENERAL] PostgreSQL, Inc Site Redone ...
>
> > On Tue, 24 Aug 1999, The Hermit Hacker wrote:
> >
> > >
> > > Mor
I have tried to install the PostgreSQL 6.5.1, but I think the installation
wasn't done correctly. Firstly, in INSTALLATION step 14 it says that the
last line in file make.install.log is
gmake[1]: Leaving directory `/usr/src/pgsql/src/man'
However in my make.install.log it is
gmake[1]: Leaving
If postmaster is really running, su the user who running postmaster
(should not be root).
and run the following two commands.
$ initdb
$ createuser anyuser
According to your Linux distribution, initdb may have been performed.
(my RedHat 6.0 scripts for postgres in rc.d/ directory runs initdb.)
Hi all
I have just isolated a big problem in one of my applications and it turns out
to be a memory leak in postgresql on a VERY basic piece of functionality
It just caused a backend to grow to 133 MB in 4 hours running, which is
obviously not good
Simple piece of C code to demonstrate this:
