Peter Eisentraut wrote:
>
> I just want to verify this: when I update between the said versions, can I
> just keep the data directory around (no need to dump/restore)? Would that
> eliminate the need to run initdb?
>
> It seems like this could be made slightly clearer in the documentation.
If t
> I just want to verify this: when I update between the said versions, can I
> just keep the data directory around (no need to dump/restore)? Would that
> eliminate the need to run initdb?
>
> It seems like this could be made slightly clearer in the documentation.
No dump/restore, no initdb. Wh
I just want to verify this: when I update between the said versions, can I
just keep the data directory around (no need to dump/restore)? Would that
eliminate the need to run initdb?
It seems like this could be made slightly clearer in the documentation.
--
Peter Eisentraut
PathWay Computing, I
I am trying to get referential integrity working with cascading deletes
and updates. The deletes work fine but updates seem to have a problem. For
example,
CREATE TABLE "master" (
id int
);
CREATE
CREATE TRIGGER "master_refcheck"
BEFORE DELETE OR UPDATE ON "master" FOR EACH
I'm having the following problem with functions and triggers (and it
isn't an SQL problem.)
With PostgreSQL version 6.4.2 when I try to use a function or trigger
(either in C or plpgsql) I get the following message:
ERROR: Load of file /usr/local/pgsql/lib/plpgsql.so failed: ld.so.1:
/usr/local
DBVer: 6.5.0, downloaded on 5/25/99
Linux: 2.0.35
Compaq 450MHz PentiumII with 256MB RAM and 1GB swap
I think I may have dug myself a deep hole. But hopefully someone
can help me climb out.
I was vacuuming my database, with analyze on; the vacuum was killed,
and I found I could no longer access
