Re: [SQL] Killing Postmaster
It's not a machine I look at often, and I realiased that it's database had never been vacuumed and had grown to about 2 gigs It is a dual PII 450, with 384 megs and U2W disks... but I started the vacuum about 10 days ago.. and when I checked it hadn't finished... I guess I'll kill it and try in verbose mode! or perhaps kill it and upgrade to 7! On Wed, 28 Mar 2001, Poul L. Christiansen wrote: > A week? That sounds much too long to me (assuming that you have > PostgresSQL funning on fairly good hardware). > > There could be something wrong with at specific table. Try to vacuum a > table one at the time using "vacuum verbose MyTable", and report any error > you may find. > > I don't understand the output of a vacuum verbose, but I'm sure other > people on this list do :-) > > Poul L. Christiansen > > On Wed, 28 Mar 2001, A James Lewis wrote: > > > > > I have a vacuum which has been running for about a week, is that too long? > > > > On Wed, 28 Mar 2001, Poul L. Christiansen wrote: > > > > > On Wed, 28 Mar 2001, Graham Vickrage wrote: > > > > > > > Hi All, > > > > > > > > What is the correct way of killing postgres 7.0 on redhat linux. > > > > > > "man pg_ctl". > > > > > > > > > > > Is there a reason why vacuum hangs on a DB with about 1.5 million rows? > > > > > > Vacuum can take a long time with 1.5M records. How long have you > > > waited? Is there any error message? > > > > > > Poul L. Christiansen > > > > > > > > > ---(end of broadcast)--- > > > TIP 4: Don't 'kill -9' the postmaster > > > > > > > A. James Lewis ([EMAIL PROTECTED]) > > If your OS needs a virus detector... RUN!!! > > ...Out and get Linux! > > > A. James Lewis ([EMAIL PROTECTED]) If your OS needs a virus detector... RUN!!! ...Out and get Linux! ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [SQL] Killing Postmaster
I have a vacuum which has been running for about a week, is that too long? On Wed, 28 Mar 2001, Poul L. Christiansen wrote: > On Wed, 28 Mar 2001, Graham Vickrage wrote: > > > Hi All, > > > > What is the correct way of killing postgres 7.0 on redhat linux. > > "man pg_ctl". > > > > > Is there a reason why vacuum hangs on a DB with about 1.5 million rows? > > Vacuum can take a long time with 1.5M records. How long have you > waited? Is there any error message? > > Poul L. Christiansen > > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > A. James Lewis ([EMAIL PROTECTED]) If your OS needs a virus detector... RUN!!! ...Out and get Linux! ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: Calling Java from psql (was Re: [SQL] requesting help)
Before I go investigating this, is it possible to trigger an arbitrary program from the SQL, say a shell script? Also, why am I getting "not subscribed messages", I am subscribed since I'm replying to a message that was sent to me!! On Thu, 29 Mar 2001, Peter Mount wrote: > At 21:37 26/03/01 +0200, Mathijs Brands wrote: > >On Mon, Mar 26, 2001 at 07:00:43PM +0200, Peter Eisentraut allegedly wrote: > > > Mathijs Brands writes: > > > > > > > Has anybody ever tried calling Java code from a pgsql trigger written > > > > in C? Shouldn't this be possible using JNI? > > > > > > I have, and given the current Java implementations it's a desaster. > > > >That bad eh? Well, I must admit I couldn't get the PHP-Java coupling to > >work stable either :( > > Not having looked at the PHP-Java link, are they working as one process or > is it some IPC type link? > > PeterM > > > ---(end of broadcast)--- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly > A. James Lewis ([EMAIL PROTECTED]) If your OS needs a virus detector... RUN!!! ...Out and get Linux! ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
