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 1iDCp0-0002fU-GZ for pgsql-performance@arkaria.postgresql.org; Wed, 25 Sep 2019 19:19:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iDCoz-0005Z2-BZ for pgsql-performance@arkaria.postgresql.org; Wed, 25 Sep 2019 19:19:29 +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 1iDCoy-0005Yo-Vk for pgsql-performance@lists.postgresql.org; Wed, 25 Sep 2019 19:19:29 +0000 Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iDCov-0004uN-Tt for pgsql-performance@lists.postgresql.org; Wed, 25 Sep 2019 19:19:27 +0000 Received: by mail-wm1-x343.google.com with SMTP id y21so6214956wmi.0 for ; Wed, 25 Sep 2019 12:19:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=M4kqv1+dIEh8iWMtFDaOS5gFjc+bne1AFIBKgvDGdcQ=; b=rErlDovvDYQg8/qUnXrL0r7DIM4AE++ZDxJT2Rkkm+z7Ksw2kGTui7+9ka9jEPJlf0 TMmOhMcmrKe8Ujwr+c1NEN8cDo0KL9oxbzJsAL3GQBvi/wJ5CCV3aI4eRzjQOAWJWxbe 9BuEZ4TdUqP6K6y6JsDy7QLXftgMZ4GY/x7XUtMbLGrdiwEOCcJ7/5XBe40aMkatMjGN aV5EGB2iUhQ9Rg9wLgkGAFqplFwpfS1LoUa/Ll5ZYctcsa5o34rzwq7CG4hXNQYAzmuA zmF9KU6Dti8fXOWnt7bvr4jLRe/FjvhfYOyQCqBKEbMHeh7bbtFa9y5cT4FSI5hGjdmO dHRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=M4kqv1+dIEh8iWMtFDaOS5gFjc+bne1AFIBKgvDGdcQ=; b=VZYJWQ67P2tWaUYLyt90VLJG0UfzHHfTIALicefKVncOeRBHWkIUbT0Ab8nucXXzBl 60OvD9ETiMAXCeNxituxrKn2Ajf6beo68S1KOZ/+ZviWhLfiD9EJfzOGZrmCUTKcoMSq BnMxCllxIoGsXGJ81UOitYJ/JETNTvnx6j7G+PG7ZCaGCDw39KTHdyzKPHBJXssT+WMR puvZViHjGSr8ojmtW+ya4nIcgvT56RZxd+AHOCb48vWyr3JPOkSyKOD4h01l8vFlZudV 2qlACvQ7AoUlONlY8aVUCmDKv4pU7Z/cE+YKogQxAmAXK3TEIeggBk4EV7dNccSZJBbH PPAA== X-Gm-Message-State: APjAAAWX0MWalLmzq+A6w1sIjnupLnCDqLdticAQGLFb8V1WEezobyK8 00sG2PdlqM2djPBj0Dm7pXFDJpq8LlI= X-Google-Smtp-Source: APXvYqz/HjUeEG1ZWqLOpE3TG0Ianab+vwfGfX6AZKv1OAvUmEk4S6l3waMBhYT0EVLWdSeqJGA9aA== X-Received: by 2002:a05:600c:40f:: with SMTP id q15mr8626323wmb.23.1569439164390; Wed, 25 Sep 2019 12:19:24 -0700 (PDT) Received: from localhost.localdomain (mobiledyn-185-69-244-96.mrsn.at. [185.69.244.96]) by smtp.gmail.com with ESMTPSA id h125sm6707843wmf.31.2019.09.25.12.19.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Sep 2019 12:19:23 -0700 (PDT) Message-ID: Subject: Re: sequence depends on many tables From: Laurenz Albe To: Mariel Cherkassky , pgsql-performance@lists.postgresql.org Date: Wed, 25 Sep 2019 21:19:22 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.4 (3.32.4-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 2019-09-25 at 15:39 +0300, Mariel Cherkassky wrote: > select objid,refobjid::regclass from pg_depend where objid=16704; > objid | refobjid > -------+------------------------- > 16704 | 2200 > 16704 | table_A > 16704 | table_A > 16704 | table_A > 16704 | table_B > (5 rows) > > for unclear reason, both table A and table B depends on the sequence. > When I check table_A I dont see any column that might use it.. Could you select all rows from pg_depend so that it is easier to see what is going on? Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com