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 1pOANP-00072z-56 for pgsql-general@arkaria.postgresql.org; Sat, 04 Feb 2023 04:42:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pOANO-0006hb-0L for pgsql-general@arkaria.postgresql.org; Sat, 04 Feb 2023 04:42:10 +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 1pOANN-0006hR-Lo for pgsql-general@lists.postgresql.org; Sat, 04 Feb 2023 04:42:09 +0000 Received: from mail-ot1-x330.google.com ([2607:f8b0:4864:20::330]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pOANL-00049W-TZ for pgsql-general@lists.postgresql.org; Sat, 04 Feb 2023 04:42:09 +0000 Received: by mail-ot1-x330.google.com with SMTP id x26-20020a056830115a00b0068bbc0ee3eeso1966961otq.0 for ; Fri, 03 Feb 2023 20:42:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:references:to:from :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=g/ELcP6sU6NcLKblW20w+qm7gS2IMWHfIkthu8aRQTk=; b=IUjxUHsujsyIR2AJ9x9UL5/OmMpKu6+3UPATfy9LmCXiA28mP8UrTOyP+QZ5QfTGSB baju0GKKOCFvyFKbLyWNaDxTD+VNCyrGSGpnx6HmbMl28qFADNUx6YJecCYzZD30ikp+ vOrQKVaBzVOEdozg/7IFa6v1TNltlGev6mfGYBstGk7XxCi2i7L+iG/XJ5yM93HPP5fY YpI/V9ffx1SCftlkA+t2wMbmq1vqEHdgADMuFEC+0kP0hMOszegplcuGnHoMV6Q+fdJ0 uOi+HGPdWCcq20bslyQG45EUrPGbmiWT9dSpaAT3ywo6Dstu1Knw9xytfvs1wT+SPseo /+KA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:references:to:from :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=g/ELcP6sU6NcLKblW20w+qm7gS2IMWHfIkthu8aRQTk=; b=7w5v7SyWtzxnxiXXybQ8ayrTOf8ODi+GQFZsiTA8UL0iGJ5Pv99qZFvsb/OPB1KiGg LsQGxUxIuTVpalrkLGvKqFPxfBWt2hRouck9uubw9C7gtV8Pin9sDRuiylFGwevrw/gZ 3Z+bjYDNbHyHLdvQx6Agk3Y3jytHLMDIsO7vqSTe4d8ObWN6/kDnm9v09o/rJntuJdrV vdG2ML2D56mXkor6wE299QIE2wu0dX9p9TmXRwUD/1HzYB5d2Eydph57Qfs+hExLL057 z7kiYYw/mKIaZljXdhSYAbk64fKkQD6mzDtD4MNj5nSp4Cjaex0wp6YHtNO+v3GFrzZs R/fw== X-Gm-Message-State: AO0yUKUt3V5HljJIeEL25LOHnIxgRIB6zhjJY4fkri2uQ7tQT8Rsv9ec MLjMQZuVaxlGCSUfw4iIV9HefGyzv5w= X-Google-Smtp-Source: AK7set/Wq2k9m5A4+/ToiyhKgic2gZ77nZREh7Pb24S4tQiY77y9WGJ3GoCO4qg17mz902W6zKyxaw== X-Received: by 2002:a05:6830:6707:b0:68b:da6c:3ec6 with SMTP id cr7-20020a056830670700b0068bda6c3ec6mr7866133otb.25.1675485725864; Fri, 03 Feb 2023 20:42:05 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id s6-20020a0568301e0600b0068bd9a6d644sm1956939otr.23.2023.02.03.20.42.05 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Feb 2023 20:42:05 -0800 (PST) Message-ID: <3410451d-667f-b198-0d06-17a998c144b5@gmail.com> Date: Fri, 3 Feb 2023 22:42:05 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: Switching identity column to serial Content-Language: en-US From: Ron To: pgsql-general@lists.postgresql.org References: <1828022907.15226.1675472079824@office.mailbox.org> <0400e92f-0d77-4276-be50-6e16321f4ae0@gmail.com> In-Reply-To: <0400e92f-0d77-4276-be50-6e16321f4ae0@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/3/23 22:41, Ron wrote: > On 2/3/23 18:54, Erik Wienhold wrote: >> I was wondering if it's possible to drop a column identity (not the column >> itself) while keeping the attached sequence. This would avoid recreating >> an identical sequence (especially with a correct start value and owner). > > Why doesn't this work? > BEGIN; > DROP SEQUENCE t_id; > CREATE SEQUENCE new_t_id_seq AS INTEGER OWNED BY t.id; > ALTER SEQUENCE new_t_id_seq OWNER TO new_owner; > SELECT setval('new_t_id', (SELECT MAX(id) FROM t)); > SELECT nextval('new_t_id'); > COMMIT; Note: this was not tested... -- Born in Arizona, moved to Babylonia.