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 1mrbAk-00007c-An for pgsql-admin@arkaria.postgresql.org; Mon, 29 Nov 2021 07:33:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mrbAi-0006wo-Ky for pgsql-admin@arkaria.postgresql.org; Mon, 29 Nov 2021 07:33:56 +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 1mrbAi-0006we-1V for pgsql-admin@lists.postgresql.org; Mon, 29 Nov 2021 07:33:56 +0000 Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mrbAe-0004Rl-Mw for pgsql-admin@lists.postgresql.org; Mon, 29 Nov 2021 07:33:55 +0000 Received: by mail-wr1-x42a.google.com with SMTP id u1so34556101wru.13 for ; Sun, 28 Nov 2021 23:33:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=V/jDrzqT/GnxRKVfouZtUeGkhatG/JFSCba+gGMJ/Ew=; b=pzbtEQ1AIG0yYVMOba7rPulGq9O9gYTT5DWoijbJtcuEhwtNf5D/FWx+ZTZ14hfAAn HvJddPD7K1xp3xSI8XEOYgZcJWji7W54RMmZlmnroPmI2kpbQb9BtrF8RCwwvTotxQDL gKX/WFGTup5SQIQkksSfbyRFj6i3OA2Rf+8kcn6wxLcj/iKEWUn20E1KU5ezsfwekPtk dE8vp/rz+IXXk84zgPcjVMdieg4Ts2PBUcq46PBsopbobwKPLzK8HNG5HYXQWWxtUsRK vRTpuJ0Z90mhByZgiQQJLxby9zP5BY3lUvWQXlyAQrW+YRj6BvQ5KvqPBELAyXNw1TXb 2BDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=V/jDrzqT/GnxRKVfouZtUeGkhatG/JFSCba+gGMJ/Ew=; b=pgy9HlMxwqZLcqiA8xJVvVxmXkeVmVI8YqT8uA83HrGB8TgDWFJBxyWvhO4DHfP8fZ +KEoa/vPoRG1go9of8KYJizdez0r/K6Gfe5GBxsH9JJBjXiyAjwQ6XC7pXiA8sAW6V9o Mt1coa0Mf4N11JjeYaURA4DlXCyUADTKYd8OHbCuwS+9z9oXbLVVubzkISCxRPiuYsje 22fRjXl9wpfoNHdYCtkKlZbU1jBCma1CvKvhHg2SztfhIwKLuf7FiKU6IGFEcHL2JS7a gheWxcZ5uywVFWufl7F/7UI6bQP8SZZvPs9OV/qTkNAaAoUZbmbpMtiWaiNrDkFwb8Bm J0ug== X-Gm-Message-State: AOAM531RGVhqmsnI/+tmJPxZl8J0Q3tBZZ1NlE897y+T0DumUDrf4TEq 5kJ06DLyky2X51AgqiUoqbwx6g== X-Google-Smtp-Source: ABdhPJwhMIUwlGQsV6f2RmZLx0MFpiy1eNDa1vnbzmzkXzFLrQ2OAklVP/2om+lLum5hsqEnd3bmOQ== X-Received: by 2002:a5d:4b41:: with SMTP id w1mr32228456wrs.537.1638171230880; Sun, 28 Nov 2021 23:33:50 -0800 (PST) Received: from localhost.localdomain (dynamic-ea4f9arkm1p81uunf-pd01.res.v6.highway.a1.net. [2001:871:5e:443:7ad9:1b6c:f621:87ab]) by smtp.gmail.com with ESMTPSA id bg34sm18130228wmb.47.2021.11.28.23.33.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 28 Nov 2021 23:33:50 -0800 (PST) Message-ID: Subject: Re: PGXN installation failure for Postgres Image of PostgreSQL 12 and 13 versions. From: Laurenz Albe To: Gaurav Anand , pgsql-admin@lists.postgresql.org Cc: Swapnil Sonawane Date: Mon, 29 Nov 2021 08:33:49 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2021-11-29 at 12:15 +0530, Gaurav Anand wrote: > Hello Team, > > Our existing DB's are working with temporal table extension. We added this from the PGXN site and it works very well for PG 9 or 10. > > Now, we are trying to upgrade our DB's with PG 13. Hence I tried to install the same pgxn extension to enable the temporal table. But I am receiving the error like postgres.h file not present and > incompatible functions in versioning.c file > > Here are the steps: > apt-get install pip; sudo pip install pgxnclient; pgxn install temporal_tables > > I tried multiple ways mentioned in the site but getting the same error. Please see the snaps attached. > > Hence having some queries about it > 1. Does PGXN ext support any of the PG 12/13/14? Any alternate ways to install it with a particular version to avoid error?   > 2. Kindly suggest a workaround if anyone has successfully tried? It may well be that the extension has a problem. You should quote the exact error messages, otherwise it is hard to say what is the matter. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com