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 1uR451-005cDG-VT for pgsql-admin@arkaria.postgresql.org; Mon, 16 Jun 2025 07:16:32 +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 1uR44z-00FqLR-Tj for pgsql-admin@arkaria.postgresql.org; Mon, 16 Jun 2025 07:16:30 +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 1uR44z-00FqLI-Fu for pgsql-admin@lists.postgresql.org; Mon, 16 Jun 2025 07:16:30 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uR44y-002Fo6-19 for pgsql-admin@lists.postgresql.org; Mon, 16 Jun 2025 07:16:29 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-ad93ff9f714so730571166b.2 for ; Mon, 16 Jun 2025 00:16:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750058186; x=1750662986; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=vzWo8ScIrdMu3Ba74LC7q/Wh6q3K2Pe8Go+v7DBin/w=; b=f0byc0qmtqa7IATU19qkW7gFj6RXU96IHAi+K5if9pFwVNTP0TxpCTnX2A2yHobev5 0RrUf/iLPEUC+KerUig+IHj3tPj0a8XyW2kYaDfJcQqKuSa6Y6ECKS+3Z0DatorQ4bO/ HBfz+JsqWTlfhKTH+7nSfpAaZkOC602M7/HYNZ30oLQhnVg/1FVwG6JLpX4GgBc6HuM7 2tyakScJxkTkpNl28T5zgNPmeoJP3+6gRccGA3fOZDsWFTmHchpaZ6sgy9ufVmrXz1ZX Fay2kqbxs25Ixni0hWRDI19lE9/5zEz9fdgwkXURaNvDkhj1gm5W6wGWo5nWsEL6yXSQ S7cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750058186; x=1750662986; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=vzWo8ScIrdMu3Ba74LC7q/Wh6q3K2Pe8Go+v7DBin/w=; b=Ih8y8gIWcvjm7PC/lK7FdlyibVlmZ1dXK6AojkD/05Czdyc6Xs+AjPRq7kfHm24NX9 e9zAoL0FT2thnFEnktzVeLHuwZ476JnMElQSH9rciaR6f61FH5hm0ulhN9halfcrKC7D SNHaMx5XS+J3Rktlj0tgMG5Mc82tuGkKC3f0qjjRT01qE0oZY62kBr5PML/vhrncnPyw GY+Idy5AIcY6ESNwIBFqt96jTti5RfxU/bhT0rQ0O1a1l+dJB9fFb2yg3u6Di1kh76Dx t4XrMvOHC6kgUx2VlraZ6S9MayCIj5QcdbLwbr6GXA8HB++L22pYkqf7lMJaJ3MK8j/K dmQA== X-Gm-Message-State: AOJu0Ywgm1Fz5qKxeGE29YDyIIB6mwngFGftaDT303e9WYPMcR/3yoiP Z193C8RiJ9X8rnzSHX59+SSGo0fW3pADXJPGU/nWpujDlNCtxlED79ZsbN3jExv9nDqhICtROC1 RvHRSHuQlcnCnO5yKn+83J76ymmRZrTKR3cOf X-Gm-Gg: ASbGncuPKjjjflznZRvmKHhuOBnbEeZB4FQ8Jfm6XdaoHCM78vUTnB19TXZC977gcL2 Fz0ZvuB4tEJzUEw56K02cU4TobZNJAgOSiDHt/8GXrTFa/EX8YandghPfbbvXN7AKd7bPMYK3TK yCMF2wgeomMjzBOQl06fncB/BZDGlUW4mezsR9AgwSqLkiTP9pkRft/MV/qvDZdzS2n+NUNafw+ PvCOwE2yAXe4lE= X-Google-Smtp-Source: AGHT+IGGrs20J+dBxpM8smntXt/dv19PitB8/1g6z5VkV6Uk3FxOYzrIQASEfVoRceRZkbcBU8ZZlCbsjT4zCfrrRBY= X-Received: by 2002:a17:907:9626:b0:ade:40cb:2517 with SMTP id a640c23a62f3a-adfad450a9amr726812566b.30.1750058185630; Mon, 16 Jun 2025 00:16:25 -0700 (PDT) MIME-Version: 1.0 From: Gambhir Singh Date: Mon, 16 Jun 2025 12:45:18 +0530 X-Gm-Features: AX0GCFsdswxA4ESfas289lUF9DnZgIoIoEUw965CjMRo8H7Q-szk9xQq3V790SM Message-ID: Subject: alter the datatype of Partition Key To: Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000007daa020637ab2cf8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007daa020637ab2cf8 Content-Type: text/plain; charset="UTF-8" Hi, We have a partition table with partitioning type range and got the requirement from the application team to alter the datatype of partitioning key from bigint to varchar. Please suggest to me the way how this can be achieved. Data volume is quite huge in the table. ~50 Billion rows -- Thanks & Regards Gambhir Singh --0000000000007daa020637ab2cf8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

We have a partition table wi= th partitioning type range and got the requirement from the application tea= m to alter the datatype of partitioning key from bigint to varchar. Please = suggest to me the way how this can be achieved.

Data volume is quite huge in the = table. ~50 Billion rows

--
Thanks & Regards
Gam= bhir Singh

--0000000000007daa020637ab2cf8--