Re: [GENERAL] Questions about horizontal partitioning

Tom Lane <[EMAIL PROTECTED]> wrote: John Sales writes: > By doing this, I'm hoping that the query optimizer is smart enough to see > that if a query comes in and requests only the six columns (that are in the > narrower table) that PostgreSQL won't have to load the wider table into the > buffer

Re: [GENERAL] Index vacuum improvements in 8.2

8.0.x has the problem that VACUUM FULL on a table does not reclaim space from the indexes, and I have to issue a separate REINDEX command. Has this been fixed in later versions? ---(end of broadcast)--- TIP 5: don't forget to increase your free s

[GENERAL] Database "postgres"

I assume it's harmless to drop the database named "postgres" (named after the DB superuser)? ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org/

Re: [GENERAL] Database "postgres"

"woger151" <[EMAIL PROTECTED]> writes: > I assume it's harmless to drop the database named "postgres" (named after > the DB superuser)? You might want to recreate it afterwards, since various tools expect it to be there (for instance createdb, createuser, "psql -l" will all fail by default if it

Re: [GENERAL] Database "postgres"

"woger151" <[EMAIL PROTECTED]> writes: I assume it's harmless to drop the database named "postgres" (named after the DB superuser)? You might want to recreate it afterwards, since various tools expect it to be there (for instance createdb, createuser, "psql -l" will all fail by default if it is

Re: [GENERAL] TRIGGER BEFORE INSERT

Uuups... That's what I feared of. I was a bit hasty and nervous after I've discovered, that the old schema doesn't work. Sory for that. An yet, the original question remain. After I've change the TRIGGER to "FOR EACH ROW", I get: --- database=# C

<    1   2