From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] destroydb doesn't close connection with client (httpd <-> pg) |
Date: | 1999-06-12 21:27:47 |
Message-ID: | 3.0.1.32.19990612142747.00774d08@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 04:58 PM 6/12/99 -0400, Tom Lane wrote:
>If you have an active website using a database, what are you doing
>destroying the database? We're not talking about dropping a temp table
>here... I find it hard to imagine what you'd use this "feature" for,
>except for shooting yourself in the foot.
Or upgrading Postgres :)
Just joking...Tom, you're absolutely right, by definition a web
site being backed by a db that's frequently created and destroyed
is not a 24/7 site. It it's not 24/7, then you can knock it down,
destroy and re-create the database, then coax the postmaster and
webserver back into service.
Most active web services will be denying some level of service
if you simply drop a (non-temp) table. The destroy the whole db?
Omigosh!
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, and other goodies at
http://donb.photo.net
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 1999-06-13 00:10:17 | Re: [HACKERS] Re: [PORTS] Patch for m68k architecture |
Previous Message | Tom Lane | 1999-06-12 20:58:47 | Re: [HACKERS] destroydb doesn't close connection with client (httpd <-> pg) |