Re[2]: Starting postmaster at boot - Mailing list pgsql-general
From | Eje Gustafsson |
---|---|
Subject | Re[2]: Starting postmaster at boot |
Date | |
Msg-id | 84194382066.20000914163101@fament.com Whole thread Raw |
In response to | Re: Starting postmaster at boot ("Adam Lang" <aalang@rutgersinsurance.com>) |
List | pgsql-general |
Is my messages coming through ?? I sent 2 messages earlier but I never saw them. Is there anyway to retrieve an expired row from a table in a database ? When you update/delete a row it's sets the old record to expired and you can not access it. When you run vacuum you delete all these expired messages if I haven't missunderstood postgres totally.. Any ideas how to display the expired rows ?? Thursday, September 14, 2000, 3:43:43 PM, you wrote: AL> OH! I get it. Whereas I have the environment variables in postgres's AL> .bash_profile, you have it set where those variables are loaded for all AL> users, correct? AL> But the part that I don't get is that (typing it at console) I can start AL> postgresql (while logged in as postgres) with the command: postmaster -i AL> because I have the variables for the location of postmaster and pgdata set. AL> But, I would assume that typing the absolute paths would have gotten around AL> that for when I was doing the su. Are there other environment variables I AL> didn't take insto consideration? AL> Adam Lang AL> Systems Engineer AL> Rutgers Casualty Insurance Company AL> ----- Original Message ----- AL> From: "Mitch Vincent" <mitch@venux.net> AL> To: "Adam Lang" <aalang@rutgersinsurance.com> AL> Cc: "PGSQL General" <pgsql-general@postgresql.org> AL> Sent: Thursday, September 14, 2000 4:40 PM AL> Subject: Re: [GENERAL] Starting postmaster at boot >> The reason I didn't have to use the -l is that I have everything AL> PostgreSQL >> needs (as far as environment variables) already set, because this machine AL> is >> a dedicated PostgreSQL server. >> >> Sorry, should have thought about that before I replied but it seems you AL> have >> it running now, that's great.. Good luck! >> >> -Mitch >> >> ----- Original Message ----- >> From: "Dale Walker" <dale@icr.com.au> >> To: "Adam Lang" <aalang@rutgersinsurance.com> >> Cc: "PGSQL General" <pgsql-general@postgresql.org> >> Sent: Thursday, September 14, 2000 1:33 PM >> Subject: Re: [GENERAL] Starting postmaster at boot >> >> >> > Adam Lang wrote: >> > > >> > > I didn't directly use your method, but you nonetheless solved my >> problem. >> > > >From the beginning everyone was telling me to put this into my >> rc.local: >> > > su postgres -c "/usr/local/pgsql/bin/postmaster -D >> /usr/local/pgsql/data -i >> > > /usr/local/pgsql/postgres.log 2>&1 &" >> > > >> > > It was never working. I noticed you had a tag "-l" in yours for su. AL> I >> > > looked up the reason for it and gave it a try. So the script: >> > > su -l postgres -c "/usr/local/pgsql/bin/postmaster -D >> > > /usr/local/pgsql/data -i /home/postgres/postgres.log 2>1 &" >> > > does work. >> > > >> > > I still don't understand the point of the 1's and 2's in the command >> though. >> > >> > >> > it's a method for redirecting STDERR --> STDOUT >> > >> > this is especially usefull in scripts >> > >> > normally I use [scriptname >/dev/null 2>&1] to send any unwanted output >> > to /dev/null >> > >> > > >> > > Why is everyone else's script working without the -l and mine wasn't? >> > > >> > >> > >> > '-l' uses the login profile for the su'd user... this is similar to a >> > 'simuated login', without it , it was only referencing variables from >> > your roo profile ... (ie. no PGDATA,etc..) >> > >> > >> > -- >> > Dale Walker dale@icr.com.au >> > Independent Computer Retailers (ICR) http://www.icr.com.au >> > ICRnet http://www.icr.net.au >> > Best regards, Eje mailto:MacAhan@fament.com The Family Entertainment Network http://www.fament.com Phone : 316-231-7777 Fax : 316-231-4066 - Your Internet Solution Provider & PC Computer Solutions Provider -
pgsql-general by date: