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.96) (envelope-from ) id 1vaKZT-0071AR-0N for pgsql-general@arkaria.postgresql.org; Mon, 29 Dec 2025 21:14:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vaKZQ-000kQa-33 for pgsql-general@arkaria.postgresql.org; Mon, 29 Dec 2025 21:14:29 +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.96) (envelope-from ) id 1vaKZQ-000kQS-1p for pgsql-general@lists.postgresql.org; Mon, 29 Dec 2025 21:14:29 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vaKZP-003Eh6-2Q for pgsql-general@lists.postgresql.org; Mon, 29 Dec 2025 21:14:28 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-79028cb7f92so13460117b3.2 for ; Mon, 29 Dec 2025 13:14:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1767042866; x=1767647666; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=vu9JWIEZ/rZpz6VxXja/sFBBaNp3tYlCbt3UEP+pr2E=; b=kXntPudVLp4OtE47JlAMSFyrg0onrBINnCEAEVtzbnyLXjQyIUq58XNUDeNb997yQi Qnz0bILhvI3/VlKw/mEJZ3FFJHyrJmVI3dHix9ksjnIv3CTPV6Am3g4TqDQGvZI9MIF9 8zklu6UYknhIuaZkzJHu3dHY4X7HedgWQ8hrcb3rrI+1AII7+I0EisIxKk6V43Sr3Jf1 lk3500+G2Odbw8s490T+qr5NcumvmxfHQ9+l9lk1UtQCV2/VRsv5UrVBmndPP22yYLZk FJ3Vw3bb0kXi25vXBsHnQ0Lbi9AkLF7Wr8RX1R8g3DgZbCTqVA0fo5Yn+gtpEXYKsLC7 508g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767042866; x=1767647666; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=vu9JWIEZ/rZpz6VxXja/sFBBaNp3tYlCbt3UEP+pr2E=; b=LKPww/sZZTeo6W5iUkiBFaq3V4XF16JRBpxD835K56QOYnWHKgNuKPS6e+J276uh2W 3ZjAP47Sc7dBc7MvbhLBmCs/snxzr/OPpibRittmmxMkESLRsIeVk+X2HvgbhCnOGX/h sEv7M8rbgXB3hIjbpHURbL9FhvcNcv211DWC9snybWIqw07uOfZ6oAgMH5I8J0Mf4uXw C2e6JEBhrPnc+jQc4YlvjIFssGBa0iAJJFKGYKk54S5pkgYx6I4FUp9QiGwmTaonHekX kGGSnpcXD5KBR2VI0uOHL8hQ3mSrEXFPrmhSu18VflPDNbhaTTUkUZc8gOQSIxFbqSQK HBsA== X-Gm-Message-State: AOJu0YyaZzIiSu1zZVDiHcm8DNy0o1GBQKwYfTO5KqAkpXJuaRh9QwZ7 TpPngLzERPd+R6UkhraHJj4xGEZEP3RzbcXIs8WkfwXwy2Gfaq3AbVLByysGnoydea/UHZiv2X1 6pZILpksvQzPKyqko3d+mCTT0LnmlYDQtWcjaa/Q= X-Gm-Gg: AY/fxX5/M9uSgXkWUDGXqiSf5cmEIkBf3cI1xPa2gOLXw/245a0GK1FZTfluFqa4Sre o2u6HChUE4OAcOorm7++jhgHjAZCp1YIlXhtqj5EgYT9+7W7fI+1SNeDCU46LkQfmRAOciDpFEl bkdBBDJ1jGGzHrx8qHrX6RMSWtNy+MP4qUuLf094c9nWcyFPhYYszL3qz71P7jP45GWHzqegORg HhSLVk7b0b9bN1G/VVl7nulAGLttwjpzO2tV5l/JQx75UhEL9S2ReOF6I4es6hJ/gA2hbI= X-Google-Smtp-Source: AGHT+IH4RSZux9a0VMGRaaBgAZTqtZB2LNNEaj6IAA+eNR/SDzWiMziO7qFSnImngyWosr4Y3yv1JjufLQ9G0AKFwMo= X-Received: by 2002:a05:690c:7092:b0:786:a8bd:3511 with SMTP id 00721157ae682-78fb3ed531dmr260714497b3.4.1767042866289; Mon, 29 Dec 2025 13:14:26 -0800 (PST) MIME-Version: 1.0 From: Igor Korot Date: Mon, 29 Dec 2025 13:14:13 -0800 X-Gm-Features: AQt7F2rw9ZPwcex2XH32OdH02gChgx9gaC0_4CooAV8aal5uN9yRMzesztUHbI0 Message-ID: Subject: PQprepare result To: "pgsql-generallists.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 Hi, ALL, [code] PGresult *res = PQprepare( m_db, "query1", ... ); PQclear( res ); res = PQprepare( m_db, "query2", ....); PQclear( res ); [/code] I presume that it is safe to do the code like this (re-using the PGresult variable). Or I have to use its own PGresult for each PQprepare call? Thank you.