Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dZAtu-0005cg-L4 for pgsql-general@arkaria.postgresql.org; Sun, 23 Jul 2017 07:02:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dZAtt-0006gp-KR for pgsql-general@arkaria.postgresql.org; Sun, 23 Jul 2017 07:02:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dZArT-0002FI-5Q for pgsql-general@postgresql.org; Sun, 23 Jul 2017 06:59:31 +0000 Received: from mail-wr0-x22c.google.com ([2a00:1450:400c:c0c::22c]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dZArM-0002pP-I9 for pgsql-general@postgresql.org; Sun, 23 Jul 2017 06:59:29 +0000 Received: by mail-wr0-x22c.google.com with SMTP id y43so95117477wrd.3 for ; Sat, 22 Jul 2017 23:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=oqOyBGM4aVXzPQ49keO1Bk0IU+cbd9M8dMfMEmDLyUU=; b=tU2Umo+CttJV9nHWqE54b0twYvasGuPB3IuqSsI6c9nNSzFYUaD4DckSFT2n2tvPUD rWDwEKnHJ+QUmMhUQzzKW/JUrfR0lSaHf8e6594OAR3BKyhwlidcbbI1NX7/q1QeNWxO w963zZi/VtFE2Df1YMdG0ZG0JlmkOtujPikcKUGRYhuXdNxAdTjJDfoTziLQ/BUXX5Gq 5BYHTA0cRb9FpOYbZLl3GWTxuJFYbcRIBajF8K9hGbjP6kuiM7fJU68OEhuIIKpjCRMU 8eUNSDzfp2oKkSJ56KXOIL+Gp9Opr1HzVnZkIu+kfvqQ6nrGlz2RgUZG2UUbgmKRi/gn 8yWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=oqOyBGM4aVXzPQ49keO1Bk0IU+cbd9M8dMfMEmDLyUU=; b=hziFcgi6e74cFUC2oU7ldkV9zQSSKxfrvCXiIw0ii3cl6Am7hbI9vaYb2lF4nF+1Qv JloLhAiG1lJOSKLKxDri3Oe0NCp/w0SI/+0ma594HH5aTYOIC/wpL8A4xmZ0BMUgNwGr xoICx0jjHPYhwbdr/gSjRBEmUCAY7ehe3w/UO9zeYsxSNOiwa2CyQ5O9ARQMpxZ8EAMQ b0Y4PjvGbxn90U/vA2TZTX+8RGYdDXTybP2KSLNwdScB2DFl8fLYmvtnXLoYE8LZNVky mUKWiAVxBnFTQU2jcvsVy3Ut0J7LWUhqXIP2UZhfpSugFE9UAoAawZjHxLm18PRgXQff fsTw== X-Gm-Message-State: AIVw111lw2KKmbg7Cjj7kMnNJTmfnvjsDZek30donBBxPfivMT4F6i3I oTjTVuSIznj7qL3G X-Received: by 10.223.173.246 with SMTP id w109mr13546247wrc.113.1500793161262; Sat, 22 Jul 2017 23:59:21 -0700 (PDT) Received: from gmail.com ([2a02:587:a41c:6300:6666:b3ff:fefa:f1f7]) by smtp.gmail.com with ESMTPSA id 34sm10200532wrt.36.2017.07.22.23.59.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 22 Jul 2017 23:59:20 -0700 (PDT) Date: Sun, 23 Jul 2017 09:59:16 +0300 From: Greg Atkins To: Tom Lane Cc: pgsql-general@postgresql.org Subject: Re: pg_dump not dropping event trigger Message-ID: <20170723065916.yarirrvszn6nf3w6@gmail.com> References: <20170722191142.yi4e7tzcg3iacclg@gmail.com> <29800.1500764403@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29800.1500764403@sss.pgh.pa.us> User-Agent: NeoMutt/20170113 (1.7.2) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org Tom, would you like a bug report to track this? On Sat, Jul 22, 2017 at 07:00:03PM -0400, Tom Lane wrote: > Greg Atkins writes: > > I have a DB with an event trigger, which I am dumping with > > pg_dump -Fc --no-acl --no-owner [db_name] > [dump_file] > > > In my dump file, I can't find any DROP EVENT TRIGGER statement. > > Well, you wouldn't, for lack of -c ... but yes, it seems you don't > get a DROP EVENT TRIGGER even with that. Will fix. > > regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general