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 1rqYcV-00D5AA-TY for pgsql-general@arkaria.postgresql.org; Sat, 30 Mar 2024 13:19:40 +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 1rqYcT-008YU6-Lu for pgsql-general@arkaria.postgresql.org; Sat, 30 Mar 2024 13:19:37 +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 1rq139-0084qA-Go for pgsql-general@lists.postgresql.org; Fri, 29 Mar 2024 01:28:55 +0000 Received: from mail-oo1-xc36.google.com ([2607:f8b0:4864:20::c36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rq131-006ySO-5Y for pgsql-general@postgresql.org; Fri, 29 Mar 2024 01:28:54 +0000 Received: by mail-oo1-xc36.google.com with SMTP id 006d021491bc7-5a1b6800ba8so664705eaf.0 for ; Thu, 28 Mar 2024 18:28:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711675727; x=1712280527; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ubbxnRrrRCKtHVlZvZSnlaCC5PtHJcI+z554Lf1u2rE=; b=HRj7n/94cDkievcYEVptKGCQ6hto703O6ACrWTYXWFL0UKh7bMUhQ89RS2Tlg7/Yx+ 52VcCADOOjlPFTCYLhGwsrw+qc75rde4njwCvzmZUp1Mye4GQFzWacdVnltqqKxmjVUz gzx/MkGF+uwCqcKaQLn6EptC8BSBnoaeqq387P8GYT+EbqMnQ3E0SlyGpIChYlIuDOmX /lj4eJu85JLE3PvssHMvTnQ3sdz4HHcLw18erg6exfWuwlw8ibHtTbP2cKT+d/uq9qss s1paD5dt1OliwAQ6G6pD9UDEDSvS1NrBpGN5Ku7XDJj0YI9F0JzmCfVXXNcQGUg8LAXZ Na9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711675727; x=1712280527; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ubbxnRrrRCKtHVlZvZSnlaCC5PtHJcI+z554Lf1u2rE=; b=m/WQnjpPIWqOv5xKoCXE0qzqIr52JtRFUVlvuvQhco3hFhvcP1CixU7BPp7eGiR3VK P9HrkxyKXFHZZ61gxlR9344qvG1U+ckGQDLe3dOPIyrZ6ggFvUHqhqWwTiSr0fY9MtyF t250182QkD5bggwv2G5GlWwGjT8Mw6mpQQe5BNpRjitBPS296pwmRjkPgmUquRE3EaAf nDJ+0+DlDLAZ8ddrcIxUr+dhVXJNkV14glmvusLgT/WsYOmITIEBAzsvCkdiGfkJcQa1 l17/2Ij0jYQZ8KSio1vdTj9GoiEy5U/VBLt6QgybnJAn0EmUQGUk5HoDdyTz73x36JV4 y5Sg== X-Gm-Message-State: AOJu0Yz2bEWKBPnwjHAlLxSGsFZqplyt2ak4a52Gf0yunxNpPu0Pj+dy WLDaYsA93R5mZMs8TeS8mzh81BE/mCh12KgbT+cp/qZk/3nrr5ggarqHJdboFwoIR2+C3f+T1Qv 3tiLspEsRRyp//29OuI6azBOIyD94DOVp57xMlA== X-Google-Smtp-Source: AGHT+IF9aYv2FPDE7NNYMZObShTaQUD9/MfiytBdWvppvYnEtywOq7YGpVwie7qYXDVfcMyhvIwYV41uvL/2lKGUYcA= X-Received: by 2002:a05:6820:210f:b0:5a1:b571:4871 with SMTP id cd15-20020a056820210f00b005a1b5714871mr875574oob.5.1711675727146; Thu, 28 Mar 2024 18:28:47 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?6buE5a6B?= Date: Fri, 29 Mar 2024 09:28:36 +0800 Message-ID: Subject: how to check if the license is expired. To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000aff47b0614c28f15" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aff47b0614c28f15 Content-Type: text/plain; charset="UTF-8" I want to develop a postgresql paid extension, then there is a local license file, how do I check if the license file is expired, check it once at each api execution, will that affect the performance of the api, is there any other way? --000000000000aff47b0614c28f15 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I want to develop a postgresql paid extension, then there = is a local license file, how do I check if the license file is expired, che= ck it once at each api execution, will that affect the performance of the a= pi, is there any other way?
--000000000000aff47b0614c28f15--