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 1jmBDA-0007WW-5h for pgsql-admin@arkaria.postgresql.org; Fri, 19 Jun 2020 07:13:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jmBD9-0006WI-2b for pgsql-admin@arkaria.postgresql.org; Fri, 19 Jun 2020 07:13:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jmBD8-0006WB-RX for pgsql-admin@lists.postgresql.org; Fri, 19 Jun 2020 07:13:14 +0000 Received: from mail-ej1-x62b.google.com ([2a00:1450:4864:20::62b]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jmBD6-0000C4-Ae for pgsql-admin@postgresql.org; Fri, 19 Jun 2020 07:13:13 +0000 Received: by mail-ej1-x62b.google.com with SMTP id f7so9073178ejq.6 for ; Fri, 19 Jun 2020 00:13:11 -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=+OVc4+PABx5QSE2akU9ftnPSj/io3hXcqjt1Yo3U9nU=; b=A6SnZknPOFI0JxDaQsM54gzTa+jqC8lBMT+cuEhiU6dMmC+X5HcJn309ntF1Wx/hIa RCkEtdlRTDRfoidrmyQ8CoXLUblggEXJe7GzyonUR3XWZaqVulTgvhV1XderpaV1Q/Iq nNBROc883WRqsOibmoZZ+2w4gZ/P27+sEem4scmU+No9YvGaQvRfbWL9MnTH8lvDbVaK srrOZjyVQmSVDRf8ACzSNAOP/Co4uUsdl/wpfbIvzqA+l8Bw7FE8WKYl0Zzc+7SXYunn 7RqIKJ/Z1w6aKTfjSUNNxDolufMIsvee6WFKMuoqCzVutzQR6BOPR/hQTtbd/+5oD0MS 0ggw== 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=+OVc4+PABx5QSE2akU9ftnPSj/io3hXcqjt1Yo3U9nU=; b=o1+1yniQSMcHNaAoQKLYBrr7BBoMgxkMgex9uXegHYOmwwjIzg0tjfwBVsvei9l5Sf Kxa3VTLMqXwaBc7yDeh7IIgOd7IOIyHqrXtK80JyDS1SaoePYbRkidz/GQUK/7f0yK6z O1DsfY16TeAO2qXWrnUZj/S0oENV48/DyxhAAn6GJi3LbjDrgk/Da2m9tCTDpWfcu6H2 MMUsoaUm+OVRTUOaNsxmM4HMb+nn5oAnLVOgRSphwDrVsXtJbxrmQAnUYBM2UM3IgpTW NXVAB38qUDB+GwNFf4v5nsSOqsmZ7SlbwBxwkgtIeogJg1S9B8BsnhtZPBY9lvI7jzxf wqRg== X-Gm-Message-State: AOAM5315csD/+4z4IEKf0UgXt2m7wjWL4VhSb6osDGSlhCnUJUYRkhxb Qd5jECL862IHa3oCT3Z+rHnBbQ== X-Google-Smtp-Source: ABdhPJwWCqLaJA3lcy/bwaJKI4saAN3XaEIi1TmIlA2Cokq9nuohUcLJhjAkd1osiQoxJzExFrA5Ng== X-Received: by 2002:a17:906:d923:: with SMTP id rn3mr2335149ejb.261.1592550790752; Fri, 19 Jun 2020 00:13:10 -0700 (PDT) Received: from localhost.localdomain (217-149-174-45.nat.highway.telekom.at. [217.149.174.45]) by smtp.gmail.com with ESMTPSA id b26sm4020766eju.6.2020.06.19.00.13.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Jun 2020 00:13:10 -0700 (PDT) Message-ID: <171a2765d49779b4ad73fc58c6a3f35acd343d04.camel@cybertec.at> Subject: Re: how to insert row with specific oid From: Laurenz Albe To: ZongtianHou , pgsql-admin Date: Fri, 19 Jun 2020 09:13:09 +0200 In-Reply-To: <99E3D554-1D96-42F0-9647-B7D2CECB3E7E@icloud.com> References: <99E3D554-1D96-42F0-9647-B7D2CECB3E7E@icloud.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-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 Fri, 2020-06-19 at 15:02 +0800, ZongtianHou wrote: > Could I insert a row to table with specific row oid. just like insert > into tbl values (xx,xx) oid=xx? Is there some syntax to do this? No, you cannot determine the OID that will be inserted. Using tables WITH OIDS is deprecated, and the feature is gone in v12. If you want to insert specific values, you shouldn't be using a system-generated OID but a regular column of type "bigint" or so. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com