Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d7HTN-0006i3-90 for pgsql-hackers@arkaria.postgresql.org; Sun, 07 May 2017 08:23:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d7HTM-0003Hy-RT for pgsql-hackers@arkaria.postgresql.org; Sun, 07 May 2017 08:23:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d7HTL-0003GQ-LY for pgsql-hackers@postgresql.org; Sun, 07 May 2017 08:23:19 +0000 Received: from mail-pg0-x235.google.com ([2607:f8b0:400e:c05::235]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1d7HTH-0002A9-W5 for pgsql-hackers@postgresql.org; Sun, 07 May 2017 08:23:19 +0000 Received: by mail-pg0-x235.google.com with SMTP id q4so20944771pga.3 for ; Sun, 07 May 2017 01:23:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=vOK+aixz/yPCYfc3r4OUFv1Jlq0pX+SVKqEbebIzsYQ=; b=DHYqjgK1KH/+o8NLPZr0NPKYWboiYGcPzBKOWr00N4wt8MUnyRkipdmQV8xR6xiGZB KCPHxzo68HWfQtjCVUd4f3BdnGD7GBgsZb2aXPFfRj6RQL/O9XlmY4JDJcxeWOIEP6rF YJ7KoJHAxL5/fIws9wp3ctYlamD2wLF7v4gMM= 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=vOK+aixz/yPCYfc3r4OUFv1Jlq0pX+SVKqEbebIzsYQ=; b=J4WWcSw1SubYXVBDkQpzQ/3yfvNl/jCa5tUO/dKs6cOaN4JNneLFy0E8RfzrjMpcIL xLN5SXpHpqb+8++VsD6LpUhoenzjlfTzr3L19fdKWf57K4/4SlqEqAS/dvkJn5YZ0qYg 8z6nJe8JCgvbhLfTxhUSGB0lAlKKbKPfxMJBdUu2z7m0tUrp3l7RcgZTuoWJS4S82ny5 yCXGLc9IWfcJeTkDoFzK6+NUZdVeOdK+IMeM3aad96CHe2jifPAajBrCdGyxtLjk2DaA U1YBQtvZSx//MCVFa4+TQVdrMy/IMZQPkHtx7qRIOMljsRHXKFWQdglJznkDQCnHonOO hSyg== X-Gm-Message-State: AN3rC/5gmX3qJjLUV1cwGcYSII4b7ctq3EQJG95PU6hApqk2djW5l4au YophoDTdGbvtdQ== X-Received: by 10.99.113.78 with SMTP id b14mr12270907pgn.223.1494145393837; Sun, 07 May 2017 01:23:13 -0700 (PDT) Received: from rfd.leadboat.com (c-98-248-47-228.hsd1.ca.comcast.net. [98.248.47.228]) by smtp.gmail.com with ESMTPSA id a21sm18905042pfc.60.2017.05.07.01.23.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 07 May 2017 01:23:12 -0700 (PDT) Date: Sun, 7 May 2017 08:23:10 +0000 From: Noah Misch To: peter.eisentraut@2ndquadrant.com Cc: Robert Haas , Petr Jelinek , Tom Lane , Michael Paquier , PostgreSQL mailing lists Subject: Re: logical replication syntax (was DROP SUBSCRIPTION, query cancellations and slot handling) Message-ID: <20170507082310.GL843225@rfd.leadboat.com> References: <27478.1493727233@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Pg-Spam-Score: -2.0 (--) 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 On Tue, May 02, 2017 at 01:42:37PM -0400, Robert Haas wrote: > On Tue, May 2, 2017 at 8:45 AM, Petr Jelinek > wrote: > > I am happy to implement something different, it's quite trivial to > > change. But I am not going to propose anything different as I can't > > think of better syntax (if I could I would have done it). I don't like > > the OFF or FALSE (ie DROP SLOT OFF) any more than what is there now and > > it also seems to not map very well to action (as opposed to output > > option as it is in EXPLAIN). It might not be very close to SQL way but > > that's because SQL way would be do not do any of those default actions > > unless they are actually asked for (ie NODROP SLOT would be default and > > DROP SLOT would be the option) but that's IMHO less user friendly. > > So the cases where this "NO" prefixing comes up are: > > 1. CREATE SUBSCRIPTION ... > 2. ALTER SUBSCRIPTION ... > 3. DROP SUBSCRIPTION ... > 4. CREATE PUBLICATION ... > So it doesn't actually look hard to get rid of all of the NO prefixes. [Action required within three days. This is a generic notification.] The above-described topic is currently a PostgreSQL 10 open item. Peter, since you committed the patch believed to have created it, you own this open item. If some other commit is more relevant or if this does not belong as a v10 open item, please let us know. Otherwise, please observe the policy on open item ownership[1] and send a status update within three calendar days of this message. Include a date for your subsequent status update. Testers may discover new open items at any time, and I want to plan to get them all fixed well in advance of shipping v10. Consequently, I will appreciate your efforts toward speedy resolution. Thanks. [1] https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers