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 1rsflA-008WKS-3l for pgsql-general@arkaria.postgresql.org; Fri, 05 Apr 2024 09:21:21 +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 1rsfl8-009eb4-7y for pgsql-general@arkaria.postgresql.org; Fri, 05 Apr 2024 09:21:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rsfl7-009eav-S2 for pgsql-general@lists.postgresql.org; Fri, 05 Apr 2024 09:21:17 +0000 Received: from mout-p-201.mailbox.org ([80.241.56.171]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rsfl2-000lMq-3r for pgsql-general@postgresql.org; Fri, 05 Apr 2024 09:21:16 +0000 Received: from smtp202.mailbox.org (smtp202.mailbox.org [10.196.197.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-201.mailbox.org (Postfix) with ESMTPS id 4V9tJf475tz9sRl; Fri, 5 Apr 2024 11:21:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1712308866; 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=qIX91aMkWQRFRRLvN6JNY6nQuCY0QFrjw+dAQwwR52g=; b=dJyTPyQ2OAmzI69Qupy1TqK5yVowN3YxzU6dTq5x+Zms63rqPjNNDk8Hke0sVSV6eAWywE p5XY7/YG1FZFVTpuf+fjUt74oY4W15PVtmRhUioyorEvSqW2GK1/P8w/VwbwN9o0/BwRcO CNkaVOkF31uUHi4jA+rJ542UjPzxpGYoPuck7DFt7ezNIJpy4Vlu7ekwJi/3EgfTbCVeNM BY7Md8l+Gm5srVSez9/aH7r/psF13MgHDpcTdoAPoWQjdpRgyn9tcyZxx3VQ8LUIWH7Ueg ubYw/mOQKCi9Z557rshO/wjLIaYy3oNvpxEmuDvL5jE9GDYYKg03Efikhg2JxQ== Date: Fri, 5 Apr 2024 11:22:32 +0200 From: Adnan Dautovic To: Tom Lane Cc: pgsql-general@postgresql.org Subject: Re: Failure of postgres_fdw because of TimeZone setting Message-ID: <8ACDD3C3-A339-4197-B918-F842921D5079@mailbox.org> References: <5DF49366-10D1-42A4-99BF-F9A7DC3AB0F4@mailbox.org> <461604.1712210044@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <461604.1712210044@sss.pgh.pa.us> X-MBO-RS-ID: 3822092a01116114ad3 X-MBO-RS-META: rdaexgquurqfcf7t9kq9nja7doqph1y3 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Tom, thank you for your reply! Tom Lane wrote: >You realize of course that PG 9.4.x is four years past EOL, and that >the last release in that series was 9.4.26, so that your remote is >missing three or so years' worth of bug fixes even before its EOL. >The underlying macOS platform looks a bit hoary as well. Yes, but this is really out of my hands. My task is to perform analysis on the remote database and my current attempt is to interface with the data using postgres_fdw in my own database, where I can put views and functions. >(You gain exactly zero points for good maintenance practice on the >local side either, since PG 13's current release is 13.14. If you're >going to install Postgres and then ignore bug-fix releases for >multiple years, I counsel not starting from a dot-zero release. >However, that doesn't seem to be related to your immediate problem.) Agreed. :-) I inherited this docker container and am in the process of getting it updated as we speak. >My best guess is that the >remote was built with a --with-system-tzdata setting that's not >actually valid for its platform. Interesting! From what I gathered, I can check the options that were used by running `pg_config --configure`. Indeed, it appears that the remote compiled their own Postgres and this is the output of the above command: '--prefix=/Applications/...' '--with-includes=/Applications/.../libopenssl/include:/Applications/.../libxml2/include' '--with-libraries=/Applications/.../libopenssl/lib:/Applications/.../libxml2/lib' '--enable-thread-safety' '--with-openssl' '--with-gssapi' '--with-bonjour' '--with-libxml' '--with-libxslt' '--with-python' '--with-readline' '--with-uuid=e2fs' 'CFLAGS=-Wno-error=implicit-function-declaration' Alas, there does not seem to be a setting regarding the timezone. Adrian Klaver's comment lead me to find out some more information. Since this thread sort of split, I would continue there. Please chime in in the other thread if you have further suggestions. Kind regards, Adnan Dautovic