> 1) Postgres 6.5.3 is a known quantity, and there are more people
familiar
> with
> the common, critical problems, so there are more people who can help
solve
> problems.
> 2) 7.0.2 undoubtedly has some new bugs and problems that are not
>apparent yet - bugs that could sink a commercial bus
ave
tested it, and are satisfied that it will work properly, then I will
consider upgrading
sooner.
jb
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Mike Mascari" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Se
Mike Mascari <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>> How do I fix this? This is on 6.5.
> 1. Change to the location of the datafiles, which, for a
> database, called "mydatabase" will look something like:
> 2. Create an empty file of the name of the index:
> 3. Delete the file u
[EMAIL PROTECTED] wrote:
>
> 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);
>
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. No
