Hi again,
Ok, for those of you who have been following my troubles with my indexes on
my site, this may interest you. I'd also appreciate any help once again,
because now I am completely foxed. It looks like shortly I will be
upgrading to 7.1.3 in a hope that this error will go away, but I'd be
i
> Since you can recreate or restore the data, erase everything in
> your $PGDATA directory and reinitialize the database.
Thanks! I'll give that a try.
> While you are at it, you should
> consider putting $PGDATA on a filesystem with more space.
Doing that has just become a priority for me! I
Since you can recreate or restore the data, erase everything in your $PGDATA
directory and reinitialize the database. While you are at it, you should
consider putting $PGDATA on a filesystem with more space.
--
Randy Hall - Red Hat Certified Engineer - Ex-Great Bridge PostgreSQL Expert
Resume: ht
Hi all-
I caused a crash by filling up the filesystem that pg_xlog lives on whilst
doing a vacuum analyze. When I looked at the remains, there were 3 WAL files
out there & no space left.
I tried simply restarting (/etc/init.d/postgresql start) in the hopes that
the mess would get cleaned, but wi
ALTER TABLE authors ADD CHECK (NOT authorfirstname = NULL);
Should that be:
ALTER TABLE authors ADD CHECK (NOT authorfirstname IS NULL);
?
Anyway, how about something like the following:
UPDATE pg_attribute SET attnotnull='t' WHERE attname='field_name' AND
attrelid in (SELECT pg_class.oid FROM pg_
