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 1o7qWb-000195-SG for pgsql-hackers@arkaria.postgresql.org; Sun, 03 Jul 2022 03:43:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o7qWa-0005t5-Mc for pgsql-hackers@arkaria.postgresql.org; Sun, 03 Jul 2022 03:43: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 1o7qWa-0005sv-DV for pgsql-hackers@lists.postgresql.org; Sun, 03 Jul 2022 03:43:56 +0000 Received: from mail-qk1-x72b.google.com ([2607:f8b0:4864:20::72b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o7qWV-0001ty-Ub for pgsql-hackers@postgresql.org; Sun, 03 Jul 2022 03:43:55 +0000 Received: by mail-qk1-x72b.google.com with SMTP id z12so4619663qki.3 for ; Sat, 02 Jul 2022 20:43:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=9JJHvp72vEEUVcydPdP5/tV45rDqGSed/CQ0zCGr0zQ=; b=WMM9d2m7S9K4JPcKjMiHbgUkq2hKnThQBWnflTUf2NN+TSRDe5gMh5T2x9U+0xDDNo hBh3TjJd/Nz34H8nbL5dxzTu8Ni7i6JtnjFpwp3/ylDZm0SukAgrWs27xJLwPHa/7qLS sTig+n5ueuk68xAIhDHHTLH8AIi3BPZP5GzXY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=9JJHvp72vEEUVcydPdP5/tV45rDqGSed/CQ0zCGr0zQ=; b=7TSITJUYSKSIiz+rMS0LgfOUuYCz1vqUXoy9MfZ04OLRH6jOSvoqUvEwrgWi89tdLi Y6+ExuGNUwESY9B5n95nwWw8Szg49G1izcBDGoBPzn7iuX4UnGCwLYGAYG4FW+AtZhfe m4xcfnY5mbzOcheCpT/5BthG5ZzvfsVvEGLxjCJb9SFutjp6GA3E9QbyrWC8j9D076rm Y7Jx3ayJZGmAUkTPtN44USrXwz9PvWllGY4CPq0wldPIrZ+YzgL0NqmhAjxcmyB9Y2TF JXKq2AmIg9+K1x4tGgQfthMENn/G4P9BBRjJnIh25zfN3It2p7cJ13GjN1hpvsIWCqot qjeg== X-Gm-Message-State: AJIora9GbgH6t+kOUWJsY+nAbkCOK8GTTpmfesYgGro0I5Exf5YYct2j LBKt0QjgG19sD2mURYkFYcD6Kg== X-Google-Smtp-Source: AGRyM1vtB0BHuhrcxSYLJwsbOeJgsOKOchnt0snhoFH4dutNkzrnjgrU4os/y+375kk+zs65ewlmFQ== X-Received: by 2002:a05:620a:2490:b0:6b1:8461:c825 with SMTP id i16-20020a05620a249000b006b18461c825mr14429025qkn.606.1656819830124; Sat, 02 Jul 2022 20:43:50 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id j12-20020ac874cc000000b00304e29c9a6asm16920463qtr.91.2022.07.02.20.43.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Jul 2022 20:43:49 -0700 (PDT) Date: Sat, 2 Jul 2022 20:43:46 -0700 From: Noah Misch To: Tom Lane Cc: Guillaume Lelarge , Benoit =?iso-8859-1?Q?Lobr=E9au?= , PostgreSQL Developers , "Dr. Michael Meskes" Subject: Re: Probable memory leak with ECPG and AIX Message-ID: <20220703034346.GC2378460@rfd.leadboat.com> References: <20211212073411.GA2218865@rfd.leadboat.com> <20220101074055.GA54621@rfd.leadboat.com> <2865639.1641054902@sss.pgh.pa.us> <20220102000750.GB54621@rfd.leadboat.com> <20220418041645.GA1134228@rfd.leadboat.com> <964681.1656788014@sss.pgh.pa.us> <20220703030619.GB2378460@rfd.leadboat.com> <1132802.1656819428@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1132802.1656819428@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Jul 02, 2022 at 11:37:08PM -0400, Tom Lane wrote: > Noah Misch writes: > > Thanks for reviewing. Pushed with that comment. prairiedog complains[1]: > > ld: common symbols not allowed with MH_DYLIB output format with the -multi_module option > > connect.o definition of common _ecpg_clocale (size 4) > > Blah. > > > I bet this would fix it: > > > -locale_t ecpg_clocale; > > +locale_t ecpg_clocale = (locale_t) 0; > > Hmm, I was considering suggesting that just on stylistic grounds, > but decided it was too nitpicky even for me. > Do you want me to test it on prairiedog? Sure, if it's easy enough. If not, I'm 87% sure it will suffice.