Hello, In file postgresql-7.4.2/src/backend/utils/fmgrtab.c
line 336 and line 337 are both equal to "extern Datum array_push (PG_FUNCTION_ARGS);" I have created a simple perl script that examines files line by line and if 2 in a row match prints a result. Sometimes it catches bad cvs checkins or copy/paste mistakes. I will continue to scan the output. Hope this helps. Mike On Tue, 2004-04-20 at 22:51, Matthew T. O'Connor wrote: > Tom Lane wrote: > > >"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes: > > > > > >>This is a good question, and I would like some opinions from some other > >>people more informed than I. > >> > >> > > > >You *can not* vacuum other sessions' temp tables; you don't have access > >to the data. (You have no way to get at pages that are modified in > >someone else's local buffer manager.) You could vacuum your own temp > >tables, if you had any, but I would hardly expect autovacuum to have > >any. > > > > > > Ok, so I will change pg_autovacuum to explicitly ignore temp tables. > Just to be sure, I can do this by avoiding anything found in the pg_temp > schemea, or is there a better way? Is it possible that a user could or > would put a non-temp table the pg_temp schemea? > > >In reference to Chris' followup question, you *should* be vacuuming > >system catalogs, and you *should not* be vacuuming TOAST tables. VACUUM > >on a regular table automatically hits the associated TOAST table. > > > > Ok, this is as I thought, pg_autovacuum is already doing the right thing > here. (see the post I just sent a few minutes ago for more details). > > Thanks Tom, > > Matthew > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
