GB in size...),
recreated it along with all constraints and indexesand everything
is fine now !!
Thank a lot for your support.
All the best,
Mario Behring
- Original Message
From: Frank Bax <[EMAIL PROTECTED]>
To: pgsql-sql@postgresql.org
Sent: Tuesday, January 16,
uei)
Restrictions of foreing key:
"fk_nodeid6" FOREIGN KEY (nodeid) REFERENCES node(nodeid) ON DELETE CASCADE
Thank you.
Best regards,
Mario Behring
- Original Message
From: Alvaro Herrera <[EMAIL PROTECTED]>
To: Mario Behring <[EMAIL PROTECTED]>
Cc: Toma
t; btree (eventuei)
Restrictions of foreing key:
"fk_nodeid6" FOREIGN KEY (nodeid) REFERENCES node(nodeid) ON DELETE CASCADE
Thanks.
Mario Behring
- Original Message
From: Tomas Vondra <[EMAIL PROTECTED]>
To: Mario Behring <[EMAIL PROTECTED]>
Sent: Tuesd
advance.
Mario Behring
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/
to
execute INCLUDES and such.If the TRUNCATE indeed free disk space, what should I
do next, reindex, vacuum ??
Also, what else can I do to avoid this kind of problem? Would a REINDEX fix the
problem and let the VACUUM command finish?
Please advise.
Thank you.
Best reg
Hi all,
Simple question: once I execute the delete statement, does it free disk space
immediatelly? Does Postgres uses something like a datafile with a pre-defined
size like Oracle does??
Please advise.
Thank you.
Mario
___
Hi list,
I have an openNMS server that uses a Postgres database. For those who are not
familiar, openNMS is an open source network management product.
Anyway, the openNMS database is very large now, more than 25GB (considering all
tables) and I am starting to have disk space issues. The openNMS
