Bruce Momjian writes:
> OID should be an unsigned int. Let us know if there are any problems.
The oid type is for storing oids, not arbitrary numbers. It might happen
to do that too, but it isn't designed for it. To get unsigned numbers use
a check contraint. Then everyone knows what's going on
Here is my $0.02 :
* when you create "id SERIAL", Postgres remembers to call function nextval on each
insertion,
* the rule's NEW.id item uses the function nextval itself instead of it's result
This explains why the ID's are what you see :
* first of all, you insert the log, calling nextval for t
Hello all,
Encountered the problem with using RULEs. Cannot log
(e.g. write some info about insertions into sepearate table)
insertions properly. Detailed description (not long or sophisticated)
follows:
I do:
1) CREATE TABLE colors (id SERIAL, color TEXT);
2) Create table for log info:
CREATE
Hi!
When perform an 'UPDATE ...' query, it was executed for 1 minute,
when I perform the query second time, it was executed for 2 minutes,
third time - for 3 minutes.
After doing vacuum the update query was executed for 1 min again.
The number of records in table updated not changed between execut
