Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ldEIg-0003ey-Oi for pgsql-docs@arkaria.postgresql.org; Sun, 02 May 2021 15:46:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ldEIe-0006dl-Fo for pgsql-docs@arkaria.postgresql.org; Sun, 02 May 2021 15:46:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ldEId-0006dd-6I for pgsql-docs@lists.postgresql.org; Sun, 02 May 2021 15:46:28 +0000 Received: from [66.111.4.26] (helo=out2-smtp.messagingengine.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ldEIV-0002A1-EL for pgsql-docs@lists.postgresql.org; Sun, 02 May 2021 15:46:26 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id DEDBE5C00FD; Sun, 2 May 2021 11:46:07 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute2.internal (MEProxy); Sun, 02 May 2021 11:46:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm1; bh=bUQYlFumBwlRsve95VpBtb4/elxdLjR Yw9zahJ9JMZE=; b=VxgTfu79bFtGBY79RO3mxeaV1Wl0yNta3OZVnbuD2F0eGSb l845J76AXSzAHRajHWkpj3LodUwOihbaSrcP2ZnwySoeBOb8EyVJPomTxXxXEAN/ wf1TQUWsC5DZXpX8ugsJv8nBnMIsQOvvzQhKT/zptejDQuZLgKV+uhzIUEOBevom 4aFW+D4670RmZWu5XpUguY1BCitUBQusb1cqAuehUIcWAKPS37KUlJbiuaEUlW6c 4IdeKLdlFvWAtS+tUp830xKRppb39pIcRpW71KQAx9flEgZRwotE64qADiKvUveA SwPPoCkNtJ107NIm3rNxhsWWger5UdFNT1DRrDA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=bUQYlF umBwlRsve95VpBtb4/elxdLjRYw9zahJ9JMZE=; b=q6u+Sp6p3jX888w2d7O8Sk yU2P/trZ4bMte1EsH//d/VWxEmMfUuPa/iPIUnh9WwcNwoZvgqbn2r1L10+o1uFj oKmCM7hcHo6beiNqOKgMOVrJLu6DDZR4SFFPbwAh1fPPF77oyP4PTcVVBUU/+i++ EYvjrFPLoc/Tv+rRJaGAKQm5PUvbcXBhGZ2xSbuuVRTHRI+/rSapFkJ2r69Txsvw i7uF2q9cC9HMTE5iCZZ0ocGNmjyEjbAqnTKNYemZuZGzWL/LUuGRQWDVmAPM3ZBd q+mBXwsoc97dtpVxOzCi9jWDD7PK7crllNm2WaxzxTE0Yud0N/1FC1dzLGRxFVcw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdefuddgudegfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfgfhu lhgvrhcuvfgrvhgvihhrrgdfuceovghulhgvrhesvghulhgvrhhtohdrtghomheqnecugg ftrfgrthhtvghrnheptdejffeiueeigeegheeiuedtveelteetjeeitdfgheehfeeukeev ffetudejhfffnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghdpvghnthgvrh hprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepvghulhgvrhesvghulhgvrhhtohdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 30DF551C0060; Sun, 2 May 2021 11:46:07 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-403-gbc3c488b23-fm-20210419.005-gbc3c488b Mime-Version: 1.0 Message-Id: <16076ad3-7859-48f8-897f-9365588d900b@www.fastmail.com> In-Reply-To: References: <161953360822.695.15805897835151971142@wrigleys.postgresql.org> <1a565681fe54535d69e6418ef5ab55405b92beac.camel@cybertec.at> Date: Sun, 02 May 2021 12:45:45 -0300 From: "Euler Taveira" To: "Nathan Long" , "Laurenz Albe" Cc: pgsql-docs@lists.postgresql.org Subject: Re: Clarify how triggers relate to transactions Content-Type: multipart/alternative; boundary=4dd8cad9fd6240439a15023a6730e4e1 X-Host-Lookup-Failed: Reverse DNS lookup failed for 66.111.4.26 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --4dd8cad9fd6240439a15023a6730e4e1 Content-Type: text/plain On Wed, Apr 28, 2021, at 2:18 PM, Nathan Long wrote: > Gotcha. Where would I go to make the PR? > There is no such PR feature; we don't use GitHub despite of having a mirror there. As Laurenz said you should create a patch (using your preferred git command) and attach to this thread. If you prefer, you can also send the patch to pgsql-hackers ML (add the link to this thread). The next step is to register your patch to the next commitfest [1] so we don't lose track of it. For a complete reference about submitting a patch, take a look at [2]. [1] https://commitfest.postgresql.org/33/ [2] https://wiki.postgresql.org/wiki/Submitting_a_Patch Regards, -- Euler Taveira EDB https://www.enterprisedb.com/ --4dd8cad9fd6240439a15023a6730e4e1 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Wed, Apr 28,= 2021, at 2:18 PM, Nathan Long wrote:
Gotcha. Where would I go to make= the PR?

There is no such PR f= eature; we don't use GitHub despite of having a mirror
the= re. As Laurenz said you should create a patch (using your preferred git<= br>
command) and attach to this thread. If you prefer, you can= also send the patch
to pgsql-hackers ML (add the link to = this thread). The next step is to register
your patch to t= he next commitfest [1] so we don't lose track of it. For a
complete reference about submitting a patch, take a look at [2].


Re= gards,

--
Euler Taveira
EDB   https://www.enterprisedb.com/

= --4dd8cad9fd6240439a15023a6730e4e1--