Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhv9r-00E4gf-Oe for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Mar 2024 17:34:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rhv9q-00CV8E-9I for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Mar 2024 17:34:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhv9p-00CV82-UL for pgsql-hackers@lists.postgresql.org; Wed, 06 Mar 2024 17:34:22 +0000 Received: from mail-wr1-x435.google.com ([2a00:1450:4864:20::435]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rhv9m-0037Zy-EP for pgsql-hackers@lists.postgresql.org; Wed, 06 Mar 2024 17:34:21 +0000 Received: by mail-wr1-x435.google.com with SMTP id ffacd0b85a97d-33e151a1434so25994f8f.2 for ; Wed, 06 Mar 2024 09:34:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1709746457; x=1710351257; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=7swwyzdXYZ+QnJG2ANrx6BuHFAZ0smiMHVfh6zPOlKs=; b=DsvBE71+7VksIyxe2Y0nFht8M0/crLdQscX6vYKptIYf0eJuKD50PK8RUDnobN5DkK plH04J5FBpuHIgYmYBln7SajN+tS6409k4DWzPO2DSWewN4DpGKhLacUDHmXROdJLvDO 9P3ugblvQQ30yHkbQ7PJA81QmKJxXEVnf90F0VXPCGUIzQTTEdFQZs/yPUmjl5q6aA2Q ViGmb92XkTmlcf0nVstlxiUUxn0srtIdFUSrbt/sauT9Qw+x4CgE0m/bNbsie1zC2kM6 53FMXOXqeiSarmjHlmIIwTGwOxoL92numPlJEm45oVhbzvVOBjarbvXK+QmTHnvCG8U9 PWbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709746457; x=1710351257; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7swwyzdXYZ+QnJG2ANrx6BuHFAZ0smiMHVfh6zPOlKs=; b=jzleGEyiq4ysKk88TnABwX4lpFd5poUNvpyUocEb0c3bBSftJIbbsns7G8ydrZ0Q4/ HSCAcLCzC3vDd5hBviEg28GjiJaam+wzoLwI80k7gI0OCy3TytuO6+wBWDCXluZGZmS4 wyoH9FjtfCLyzFv1RNuyMeuaMwerUyl5LJrh01yHrNzVhLtzkhm3+SI7qQzjyGR44C/M LuYxnqnV/dycMFbdfP+2r7tEZqWoBWTyD0oGv75bEqLlvKf24Rx0YF4visABBzd6R6y5 TwflaQrqa3VQ2+yc2W7xBHAxriJKj/Pi1A5HInV+mUx7vV4sCwzyuUcqypRmOqXbJtDI V61A== X-Forwarded-Encrypted: i=1; AJvYcCWOKDwTV+XzRA/dOuiVKCH/Nmpa4LzpKT4PcNI/mEf1llh9mbvI4eo3SNrNsTh991z+Yb4mYMqSZ/QZNCyUoB/tkuXFFD354UoTjkzFNp+VKYTw X-Gm-Message-State: AOJu0YzpCyTs694J4wYFAZvl/hIUvvOPApZ6pQI+andAf4UPY5NrMit9 Ta4tp1Evgc8q3PEYDclbV8X7ezAqmvwKSvGAAp0Nvbv8koQKO1c0+FT1c58oaw== X-Google-Smtp-Source: AGHT+IE5zl7Lr9Ybj5z9DD3b1YDHL1bqoVsq1yWPCFZwgegbUxB5HxqQ9YH1fhfTJJa/vl8xAs83qw== X-Received: by 2002:adf:f347:0:b0:33d:b2d7:6264 with SMTP id e7-20020adff347000000b0033db2d76264mr11030567wrp.51.1709746456842; Wed, 06 Mar 2024 09:34:16 -0800 (PST) Received: from [10.137.0.18] (ip-86-49-229-30.bb.vodafone.cz. [86.49.229.30]) by smtp.gmail.com with ESMTPSA id bn14-20020a056000060e00b0033e4458ccd3sm7208068wrb.69.2024.03.06.09.34.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 06 Mar 2024 09:34:16 -0800 (PST) Message-ID: Date: Wed, 6 Mar 2024 18:34:15 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: logical decoding and replication of sequences, take 2 Content-Language: en-US To: Dilip Kumar , Robert Haas Cc: Amit Kapila , Ashutosh Bapat , "Hayato Kuroda (Fujitsu)" , "Zhijie Hou (Fujitsu)" , PostgreSQL Hackers , Masahiko Sawada , Peter Eisentraut References: <996e4d3c-648a-46d0-86d2-6465f53ddc58@enterprisedb.com> <5bbadb71-b51e-45a1-9acc-d54f5e8850b6@enterprisedb.com> <241d6c00-7997-480f-80c1-636b28d457cf@enterprisedb.com> From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, Let me share a bit of an update regarding this patch and PG17. I have discussed this patch and how to move it forward with a couple hackers (both within EDB and outside), and my takeaway is that the patch is not quite baked yet, not enough to make it into PG17 :-( There are two main reasons / concerns leading to this conclusion: * correctness of the decoding part There are (were) doubts about decoding during startup, before the snapshot gets consistent, when we can get "temporarily incorrect" decisions whether a change is transactional. While the behavior is ultimately correct (we treat all changes as non-transactional and discard it), it seems "dirty" and it’s unclear to me if it might cause more serious issues down the line (not necessarily bugs, but perhaps making it harder to implement future changes). * handling of sequences in built-in replication Per the patch, sequences need to be added to the publication explicitly. But there were suggestions we might (should) add certain sequences automatically - e.g. sequences backing SERIAL/BIGSERIAL columns, etc. I’m not sure we really want to do that, and so far I assumed we would start with the manual approach and move to automatic addition in the future. But the agreement seems to be it would be a pretty significant "breaking change", and something we probably don’t want to do. If someone feels has an opinion on either of the two issues (in either way), I'd like to hear it. Obviously, I'm not particularly happy about this outcome. And I'm also somewhat cautious because this patch was already committed+reverted in PG16 cycle, and doing the same thing in PG17 is not on my wish list. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company