From: mike g <mike@thegodshalls.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Duplicate variable declared?
Date: Tue, 20 Apr 2004 23:48:49 -0500
Message-ID: <1082522928.19094.9.camel@localhost.localdomain> (raw)
In-Reply-To: <4085EFC3.9020109@zeut.net>
References: <200404201525.i3KFPp809934@candle.pha.pa.us>
<40855DF0.3010300@idigx.com>
<37398.192.154.91.225.1082485149.squirrel@192.154.91.225>
<25435.1082518142@sss.pgh.pa.us>
<4085EFC3.9020109@zeut.net>
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" <matthew@zeut.net> 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 majordomo@postgresql.org
Attachments:
signature.asc (application/pgp-signature, 188B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mike@thegodshalls.com, pgsql-hackers@postgresql.org
Subject: Re: Duplicate variable declared?
In-Reply-To: <1082522928.19094.9.camel@localhost.localdomain>
References: <200404201525.i3KFPp809934@candle.pha.pa.us> <40855DF0.3010300@idigx.com> <37398.192.154.91.225.1082485149.squirrel@192.154.91.225> <25435.1082518142@sss.pgh.pa.us> <4085EFC3.9020109@zeut.net> <1082522928.19094.9.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox