Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ipBuU-0007H5-VD for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Jan 2020 14:02:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ipBuT-0003b7-B4 for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Jan 2020 14:02:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ipBuS-0003aw-VA for pgsql-bugs@lists.postgresql.org; Wed, 08 Jan 2020 14:02:09 +0000 Received: from mail-wr1-x442.google.com ([2a00:1450:4864:20::442]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ipBuQ-0003jS-HB for pgsql-bugs@lists.postgresql.org; Wed, 08 Jan 2020 14:02:07 +0000 Received: by mail-wr1-x442.google.com with SMTP id q6so3460846wro.9 for ; Wed, 08 Jan 2020 06:02:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=0ZciBPA0FPeDXHlWNwMoIrT0EawIt/Grttjj7MUXNTQ=; b=F20s7XwSKkMyDBBm/FsLC4+4RJJORtmkSeiuSWSe56uKjH2Xrq6PwaUL/nXVnJw6kn 4+xWOVbSq2WFetqznESbj8paG1mLVpfsGUTzT1zrCdDq/hxRUPFoVgO2sFkXKHNNdTtP AesRNNAh3t1qCQ7+aDtc9vpfRaUFrarpRnL186yW3za+QVS82aDM9qC+IwvWDZinj754 OZ9i9aQZLrQASA9kZbf+hMh85U3fRkS0mHVyfFJyNZ7B9NjUwnnqi/77EMBvRmC8O8Ij IQA7WdAZtG8PedWPy/0oHxgUKhLcfnvPE/SYiLYYaQY9K/bmZCEN6jh6fHc8/zSzD4qq L+kQ== 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; bh=0ZciBPA0FPeDXHlWNwMoIrT0EawIt/Grttjj7MUXNTQ=; b=ONp5P4CvNZm/Dh1Bk2LsaIwLukcCfc8XP+4Hf+aE4G7AAj/GCJAs5ygHNwKrLZ7kBV CLWbDckZS0BYKb1LkSUDAZdZHNdnwnampPf2/WhMHXAg4VtyHYpuR2uG0UYr//o1ZsqF KtAyxXo/nOp4McbPd22sIJNJOqUxgBoQbSbHimVVGh3CaGSlGOodQw5Z3VsYoha528s6 gAFnkqyFWFkJnlEtlJ5sQMQzxOiXpJX9A8NdPoBYwJFR6qjk0vt6n2ciwBLg+H5el9GL 15eFvtm2T/p6KuWCmzQYyMP3CwV4gQcYNHbsNRwFbXQwlEJlqr695XEs3wMhp4ld9ceh APkA== X-Gm-Message-State: APjAAAW0BKRld9Wyeb2PdkUDAYpzX1g97L/h+4XbCCQLHwOfZZD/kDpn mgbFEPGn0WtAUAZm7YmLb4DH/g== X-Google-Smtp-Source: APXvYqyevsj/uOQnZGPv/pF0fdloU7UOSoaz5ElNV6SNAaC7H4riQS24XzyAOCLEi4EuO13xtTwUhg== X-Received: by 2002:adf:c74f:: with SMTP id b15mr4766334wrh.272.1578492124784; Wed, 08 Jan 2020 06:02:04 -0800 (PST) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id t131sm1884609wmb.13.2020.01.08.06.02.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Jan 2020 06:02:03 -0800 (PST) Date: Wed, 8 Jan 2020 15:02:02 +0100 From: Tomas Vondra To: Dave Cramer Cc: pgsql-bugs@lists.postgresql.org Subject: Re: publication not found, yet it is there.?? Message-ID: <20200108140202.j2chhynphzmnddyc@development> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Jan 08, 2020 at 08:35:28AM -0500, Dave Cramer wrote: >How is this possible? > >I have checked pg_replication_slots and the slot exists. I have checked >pg_publications and the publication exists. > Isn't this essentially the same issue as the one you reported about a month ago on pgsql-hackers: https://www.postgresql.org/message-id/CADK3HH%2B9uPg%3DanB-thAMojVhsZk3tYWMwux4YmHB2%2BByJXcE3w%40mail.gmail.com I don't think we really identified what's going wrong there :-( regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services