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 1sHr5s-00BDxE-Od for pgsql-general@arkaria.postgresql.org; Thu, 13 Jun 2024 20:30:48 +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 1sHr5q-007W4Z-Ju for pgsql-general@arkaria.postgresql.org; Thu, 13 Jun 2024 20:30:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHr5q-007W4M-3C for pgsql-general@lists.postgresql.org; Thu, 13 Jun 2024 20:30:47 +0000 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sHr5o-001Au4-7s for pgsql-general@lists.postgresql.org; Thu, 13 Jun 2024 20:30:45 +0000 Received: by mail-oi1-x231.google.com with SMTP id 5614622812f47-3d226c5a157so852601b6e.2 for ; Thu, 13 Jun 2024 13:30:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=musicsmith-net.20230601.gappssmtp.com; s=20230601; t=1718310643; x=1718915443; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ls6IPeeYKELOYkl9XElL16feI+YtihqeTe5xMmwBLjA=; b=X/mQ5n01yxdNsSp27k/F5omtb0Popq779U8zPB8W0BrbVdenPK56AbRFW9aWHbLHfJ nTbAe2WpyG4lmyVy7g4d2tYbU1edU/gILOFhuegbXWUKA72RLcWPzSx/5YjYwDD48J/x +RfqkJTc4dihS1gtDlaqcEdodXk5aTvecQCnXJn/Lxkun4k0jmgEB1CZU5m7aG/MRlf6 rK96JlVwxzbx7D66ggAIq7FFl9TPnudNFw994VqDqFeIg/rxDRMkzennbaVn4TfY3Mgf q8CPoYo5DLuvE20MzSEMDEVxi0bzc/DzjjHku8YBwKDm4IKuDoXI1RKMWLp2yxmxvmbm JuaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718310643; x=1718915443; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ls6IPeeYKELOYkl9XElL16feI+YtihqeTe5xMmwBLjA=; b=b9/JN1I+OKbgqRqjoJuVl0zOuCTjARWR4feLmjTvmEByS5xHjdB/QDS8um5SLVchju 6YqP2CMRhiBq9n1CeG/bJcfcqaa7Udy7YXv94OkDqPrj9C0wiwGdQoBjn8nOt+SPYTvv I0skzuEKnIwZsD8aQ3Y37TH4bYXrGdzMroI54sXai7jsReC5edeGVB3ESEPbssvUHkJ1 Gronv9aMQfmU0UwLmP0totfppszzQod2v7z6+Cf/2Z1eEo9lZHOgA92KbL3eRIxb8Er6 NhH2/LQZtg2owkTLbXSsWPW/A/hpXirDKw5wvnzEE48DrbE3fyvxpiJjVjnHPKg/7I5Y 3rnQ== X-Gm-Message-State: AOJu0YwFXf0UYVRcDSHwsXNPnOju1lKtA1l7BB1+VUVKIkt4l6KbrGKt orpxD1/TJh56iE33WElNWMmeqVYdhbnQplIBZ1tRlodWciMwqrHsBezNIsrIN9n2nUxW/ZQEJQz oRlQL0Aw2twsIeptJZ2SwfPc68y/Ut45jKKqq X-Google-Smtp-Source: AGHT+IFo20TZ+jZxmpcuPkr7x+V6WkNO8Pf0vDE+PTEP7xJlS+x1inwuHgQe9BeyifSbRucuw9V2OXVkirt9aoRa+sU= X-Received: by 2002:a05:6808:2182:b0:3d2:2877:513d with SMTP id 5614622812f47-3d24e97fa0emr734306b6e.39.1718310643412; Thu, 13 Jun 2024 13:30:43 -0700 (PDT) MIME-Version: 1.0 References: <387fa6c2-5de-f24-d522-46282597703@appl-ecosys.com> In-Reply-To: From: Jeremy Smith Date: Thu, 13 Jun 2024 16:30:32 -0400 Message-ID: Subject: Re: Reset sequence to current maximum value of rows To: Rich Shepard Cc: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Aha! So it's likely that by listing the PK column name in the list of > columns to be inserted was what caused the problem? No need to specify > DEFAULT for it? > There's no need to specify the column if it has a default value, but specifying it did not cause the issue that you saw.