RE: [HACKERS] VACUUM ANALYZE problem on linux

Hello!

On Wed, 24 Feb 1999, Dan Gowin wrote:
> What user ID are you using? Are you "su"ing over
> the the postgres user ID.

But of course!

> Also, make sure all of the environment variables
> are exported in the script. PGPORT, PGUSER, etc...

I want to remind you and all who watch the thread: I have the problem
on 3 different glibc2 linucies - heavily modified Debain 2.0, newly
installed Debain 2.0 and modified RedHat 5.1. I have no problem with
sparc-solaris, and I have a report from Tom Lane he has no problem with
HP-UX.
IWB interesting to test libc5-linux...

> D.
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Wednesday, February 24, 1999 1:35 PM
> To: phd2(at)earthling(dot)net
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] VACUUM ANALYZE problem on linux
>
>
> Oleg Broytmann <phd(at)sun(dot)med(dot)ru> writes:
> > 3. Run postmaster -b -D/usr/local/pgsql/data -o -Fe -S (to detach it)
> > and run VACUUM ANALYZE - worked
> > (I took these parameters from script /etc/init.d/postgres)
> > 4. Run /etc/init.d/postgres start
> > and run VACUUM ANALYZE - failed, no core file.
>
> So there is something different about the environment of your postmaster
> when it's started by init.d versus when it's started by hand. Now you
> just have to figure out what.
>
> I thought of environment variables, ulimit settings,
> ownership/permission settings ... but it's not clear why any of these
> would affect VACUUM in particular yet leave you able to do other stuff
> successfully. Puzzling.
>
> regards, tom lane
>

Oleg.
----
Oleg Broytmann http://members.xoom.com/phd2/ phd2(at)earthling(dot)net
Programmers don't die, they just GOSUB without RETURN.