Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TpHqr-0007Jt-9j for pgsql-hackers@arkaria.postgresql.org; Sun, 30 Dec 2012 12:18:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TpHqq-0003ML-HG for pgsql-hackers@arkaria.postgresql.org; Sun, 30 Dec 2012 12:18:48 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TpHqo-0003MF-Ti for pgsql-hackers@postgresql.org; Sun, 30 Dec 2012 12:18:47 +0000 Received: from acidenitrix.villemain.org ([91.121.90.165]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TpHqm-0004Bf-ON for pgsql-hackers@postgresql.org; Sun, 30 Dec 2012 12:18:46 +0000 Received: from [89.157.243.169] (helo=Dimitris-MacBook-Air.local) by acidenitrix.villemain.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1TpHqk-0003o3-HT; Sun, 30 Dec 2012 13:18:42 +0100 From: Dimitri Fontaine To: Peter Eisentraut Cc: Robert Haas , PostgreSQL Hackers Subject: Re: Event Triggers: adding information Organization: 2ndQuadrant References: <1356840827.20017.15.camel@vanquo.pezone.net> User-Mail-Address: dimitri@2ndQuadrant.fr Date: Sun, 30 Dec 2012 13:18:32 +0100 In-Reply-To: <1356840827.20017.15.camel@vanquo.pezone.net> (Peter Eisentraut's message of "Sat, 29 Dec 2012 23:13:47 -0500") Message-ID: User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (darwin) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org --=-=-= Content-Type: text/plain Hi, Peter Eisentraut writes: > There is a new compiler warning coming from this, I believe: I don't get this warning here, at least not in -O2, and I did forget to make maintainer-clean then rebuild with -O0 just in case gcc is now complaining about something else. I wish this situation could be fixed. Now, this warning needs to be fixed, too, and here's a patch for that. Thanks, regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=copy-warning-fix.patch diff --git a/src/backend/commands/copy.c b/src/backend/commands/copy.c index 31a0288..00f859e 100644 --- a/src/backend/commands/copy.c +++ b/src/backend/commands/copy.c @@ -750,7 +750,7 @@ DoCopy(const CopyStmt *stmt, const char *queryString, uint64 *processed) bool is_from = stmt->is_from; bool pipe = (stmt->filename == NULL); Relation rel; - Oid relid; + Oid relid = InvalidOid; /* Disallow file COPY except to superusers. */ if (!pipe && !superuser()) --=-=-= Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --=-=-=--