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 1q6vo0-0000Ip-EV for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 07 Jun 2023 16:14:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q6vnz-0001HI-CR for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 07 Jun 2023 16:14:39 +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 1q6vRE-0002M8-0k for pgsql-pkg-debian@lists.postgresql.org; Wed, 07 Jun 2023 15:51:08 +0000 Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q6vR8-000oYo-WA for pgsql-pkg-debian@lists.postgresql.org; Wed, 07 Jun 2023 15:51:07 +0000 X-GND-Sasl: cedric.villemain@abcsql.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abcsql.com; s=gm1; t=1686153061; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=vkpnCupvpfjA10ftkkj8d7UE0b+aIdPs2HanvcbsFJs=; b=FRBqFEN44kyATESmyWNwU/jm0hPqim0OibPcXow8XnHrk+8+psE5iEpzeeZO+RCzbR8P6F Iahw5jpaDQDckuSZZ+qXw6wX38YojNQbw82ylTHrisoVm3nQUQyUg2GpQUx7SDBHsvbESA hSK4b2WGd6OUBrDS8Mvg1dQ0YphtmAYqBFTkRx0rqB2afIQUeV5Gti1VMZbrLwyhVK6dFa RfFjg79zznTv6VpSGMiiHZmChZuqNHo4ZAtfTS1sXosqncIalrAdtbdqUwYcZ/CaF2bJl7 rjBwnUQab6Rdv82MgsFEEARPl0e60sV1NAj7NhakUGzQvQkn1NtXR5uSHlJDQQ== X-GND-Sasl: cedric.villemain@abcsql.com X-GND-Sasl: cedric.villemain@abcsql.com X-GND-Sasl: cedric.villemain@abcsql.com Received: by mail.gandi.net (Postfix) with ESMTPSA id 79F1AE000B; Wed, 7 Jun 2023 15:51:00 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------nXV0OPvjurIcS0mM0dnEw5Go" Message-ID: <75679669-4482-3f16-bd4d-6ec1f9950941@abcsql.com> Date: Wed, 7 Jun 2023 17:50:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Packaging request MobilityDB Content-Language: fr, en-US To: Esteban Zimanyi , Bradford Boyle Cc: pgsql-pkg-debian@lists.postgresql.org, SCHOEMANS Maxime References: From: =?UTF-8?Q?C=c3=a9dric_Villemain?= Organization: Data Bene In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------nXV0OPvjurIcS0mM0dnEw5Go Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Le 07/06/2023 à 17:16, Esteban Zimanyi a écrit : > Dear Bradford > > Many thanks for your work. Seconded! and tks for MobilityDB too ! > * We solved the stack smashing problem you found. > * We set the log_error_verbosity to terse for the tests and removed > the special treatment of ERROR, CONTEXT, and WARNING that may vary > across PostgreSQL and PostGIS versions. > * For the tests, we can easily switch to the settings 'PST8PDT' for > the timezone and 'Postgres, MDY' for the date style if this is the > general way to do things. We simply need to regenerate all tests and > push them in a new commit. We just wonder if the same settings are > equally valid for all other distributions. Please advise. > Yeah, 'PST8PDT' is the way to go for PostgreSQL test [1] I believe it's valid for other distributions. Apparently datestyle is not documented here, but pg_regress does:      /*       * Set timezone and datestyle for datetime-related tests       */      setenv("PGTZ", "PST8PDT", 1);      setenv("PGDATESTYLE", "Postgres, MDY", 1); see also [2] which might be useful as it mentions some corner cases for other systems. [1]: https://www.postgresql.org/docs/current/regress-evaluation.html#id-1.6.20.6.8 [2]: https://doxygen.postgresql.org/pg__regress_8c_source.html#l00702 --- Cédric Villemain +33 (0)6 20 30 22 52 https://Data-Bene.io PostgreSQL: Expertise - Formation - Développement - Assistance Technique --------------nXV0OPvjurIcS0mM0dnEw5Go Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Le 07/06/2023 à 17:16, Esteban Zimanyi a écrit :
Dear Bradford

Many thanks for your work.


Seconded! and tks for MobilityDB too !


* We solved the stack smashing problem you found.
* We set the log_error_verbosity to terse for the tests and removed the special treatment of ERROR, CONTEXT, and WARNING that may vary across PostgreSQL and PostGIS versions.
* For the tests, we can easily switch to the settings 'PST8PDT' for the timezone and 'Postgres, MDY' for the date style if this is the general way to do things. We simply need to regenerate all tests and push them in a new commit. We just wonder if the same settings are equally valid for all other distributions. Please advise.

Yeah, 'PST8PDT' is the way to go for PostgreSQL test [1]

I believe it's valid for other distributions.

Apparently datestyle is not documented here, but pg_regress does:

     /*
      * Set timezone and datestyle for datetime-related tests
      */
     setenv("PGTZ", "PST8PDT", 1);
     setenv("PGDATESTYLE", "Postgres, MDY", 1);

see also [2] which might be useful as it mentions some corner cases for other systems.



[1]: https://www.postgresql.org/docs/current/regress-evaluation.html#id-1.6.20.6.8

[2]: https://doxygen.postgresql.org/pg__regress_8c_source.html#l00702

---
Cédric Villemain +33 (0)6 20 30 22 52
https://Data-Bene.io
PostgreSQL: Expertise - Formation - Développement - Assistance Technique
--------------nXV0OPvjurIcS0mM0dnEw5Go--