Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YvC0u-0006qO-HQ for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2015 21:58:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YvC0t-0004qp-S7 for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2015 21:58:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YvC0s-0004qh-Bf for pgsql-hackers@postgresql.org; Wed, 20 May 2015 21:58:54 +0000 Received: from mail-qk0-f177.google.com ([209.85.220.177]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1YvC0p-0004sU-7A for pgsql-hackers@postgresql.org; Wed, 20 May 2015 21:58:53 +0000 Received: by qkgv12 with SMTP id v12so41562163qkg.0 for ; Wed, 20 May 2015 14:58:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=6o2Ptl2BoyQA/g2HQP6Fyafiwn6acYxPe4Y4PxTn3z4=; b=HMFQkU7qzqMMQEcrVq24D/Xd7n14qQ0b2ejL7s2T82i4GTy+jwHkNoaVWHn98M2HL/ fwsIPq4wVrCL8eJH2piSjSRrZFQO9YaroT0RD+l8PsjMOIDYU1NeEHFySN3lbk3Vxi6p dg17M2/cK7e8hd0VS+8NQRfmaw04/FTCXXSxX3VkPiajMqWTBvzVg3pGgAjdfETWiiS0 71znGXYK1FBWwfBrSfZMLK7o+6S/HcJixDKdYwAhXxKeYhtddF6v2x8u1YxENhN5x/LF fNX4mIToqlcRheH5ZeQF3Q8JdUdrzqJIwbak7Sxw1/xryifCFJF5xyNzK1xLFaxZ7pYj AglA== X-Gm-Message-State: ALoCoQlcsnJH1fxaPKsouzmpo6xR1obl+XokKr6pw5yHOakeOaFEUthSbcVbixX5UR4U7wKNtoZV X-Received: by 10.140.30.166 with SMTP id d35mr45420382qgd.85.1432159130177; Wed, 20 May 2015 14:58:50 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([200.85.219.137]) by mx.google.com with ESMTPSA id z9sm3392013qgz.25.2015.05.20.14.58.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 May 2015 14:58:49 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 923B920A; Wed, 20 May 2015 18:58:16 -0300 (CLT) Date: Wed, 20 May 2015 18:58:16 -0300 From: Alvaro Herrera To: Andres Freund Cc: pgsql-hackers@postgresql.org Subject: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. Message-ID: <20150520215816.GI5885@postgresql.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.6 (--) 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 Andres Freund wrote: > Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. Hm, I just realized that the command tag for INSERT ON CONFLICT is still just INSERT. Is that okay? To me, the behavior is different enough that it should have its own tag. I'm not too set on this, but maybe others share this opinion? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers