The backend died while I was dropping an index on a table. Now I cannot
access my data! Help!
My table looks like
create table user_usage (email varchar(100),date date);
I created the index:
CREATE INDEX user_usage_email_idx on user_usage(email);
When I dropped the index, the backend died. Now
I have a Postgres application that must run 24x7. If postgres needs to be
vacuumed periodically, must I take the application offline, or is it enough
to disallow write (INSERT/UPDATE) access while allowing read access?
I hope it is the latter, as I have a large data set and there are
transaction
back-ends...
>
> Nicolas Huillard
>
> -Message d'origine-
> De: brianb [SMTP:[EMAIL PROTECTED]]
> Date: mercredi 3 mai 2000 04:32
> À:[EMAIL PROTECTED]
> Objet:[ADMIN] pg_sorttemp files
>
>
> I found a couple of pg_sorttemp* files in
I found a couple of pg_sorttemp* files in my database directory. Is it safe
to delete these? They're quite large (around 40MB each) and have a creation
date of a couple of days ago.
Brian
--
Brian Baquiran <[EMAIL PROTECTED]>
http://www.baquiran.com/
AIM: bbaquiran
Is it possible for me to find out which queries are currently running? I
run some db-related tasks non-interactively via cron, and I'm suspecting
that some of them may be taking too long.
Any help would be appreciated.
Brian
--
Brian Baquiran <[EMAIL PROTECTED]>
http://www.baquiran.com/
AIM: bb
